npm-name@8.1.1
npm · checked 21 Oct 2026, 20:32 UTC · checker 2026-10-19.2 · log index 336
Record issued 21 Oct 2026
Issued 21 Oct 2026, 20:32 UTC · npm-name@8.1.1 · npm
reads credentials
An install step opened a credential file or variable. Find out why before installing.
Loading it opened files that hold credentials on a developer machine, CI runner or agent host (~/.npmrc (npm token)). A library has no business there; find out why before using it.
The trace shows what a step attempted. A quiet trace is evidence, not proof.
Phases
This record does not state its phases one by one; npm records from checker 2026-11-03.1 and Python records from 2026-11-04.3 on do.
Install steps
npm-name has no install step of its own.
No dependency runs anything at install.
What the run reached
Nothing was observed for this run.
First import
It was imported once, as an application would, and exited 0.
- Programs
- node
- Credentials read
- ~/.npmrc (npm token)
- Credentials sent
- No decoy left the box.
Dependencies
23 of 23 installed, as npm would on linux x64 musl.
Show all 23
- @pnpm/config.env-replace@1.1.0
- @pnpm/network.ca-file@1.0.2
- @pnpm/npm-conf@3.0.3
- config-chain@1.1.13
- deep-extend@0.6.0
- graceful-fs@4.2.10
- ini@1.3.8
- is-scoped@3.0.0
- is-url-superb@6.1.0
- ky@1.14.3
- lodash.zip@4.2.0
- minimist@1.2.8
- org-regex@1.0.0
- p-limit@6.2.0
- p-map@7.1.1
- proto-list@1.2.4
- rc@1.2.8
- registry-auth-token@5.1.1
- registry-url@6.0.1
- scoped-regex@3.0.0
- strip-json-comments@2.0.1
- validate-npm-package-name@5.0.1
- yocto-queue@1.2.2
Since the previous version
No comparison with an earlier version was made for this check.
Sandbox
network=none; capabilities=all-dropped; rootfs=read-only; user=nobody; harness=separate-user
Signature and transparency log
- level
- reads_credentials
- verdict
- manual_review
- reasonCode
- load_read_credentials
- keyId
- 322a2536e0d5ec8e
- algorithm
- ed25519
- checker
- 2026-10-19.2
- issuedAt
- 2026-10-21T20:32:50Z
- contentSha256
- d52586a6af8e2f1e9882e6519bf0cd49e22646d7dfbfa6081884510a4868e109
- contentSizeBytes
- 4504 (4 KB)
- log index
- 336
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 21 Oct 2026, 20:32 UTC
What this does and does not say
The claim is about the bytes, not the name.
The signature covers these exact bytes. Another version is another check.
A quiet trace is evidence, not proof.
Code that only runs later, when your app calls it, is out of reach.
A signature is not an endorsement.
It says what happened, not that the code is good.
Twenty checks an hour for each network address. When a limit is ours, the record says unfinished and names it.