pnpm@12.16.1
npm · checked 29 Oct 2026, 13:09 UTC · checker 2026-10-19.2 · log index 1058
Record issued 29 Oct 2026
Issued 29 Oct 2026, 13:09 UTC · pnpm@12.16.1 · npm
quiet
Its install steps ran with decoy credentials in reach and touched nothing we watch.
Its install steps ran here, with decoy credentials in reach, and touched nothing we watch: no network, no credential files. That is evidence, not proof: code can wait for a different machine or run later, when it is used.
The trace shows what a step attempted. A quiet trace is evidence, not proof.
Install steps
pnpm runs 2 install steps of its own:
- preinstall
- postinstall
No dependency runs anything at install.
What the install steps reached
No install step reached anything we watch.
- Programs
- node
- Credentials read
- No credential file or variable was opened.
- Credentials sent
- No decoy left the box.
The record keeps what all the install steps reached together; it does not say which step did which.
First import
It was imported once, as an application would, and exited 1.
It reached nothing we watch.
- Programs
- node
- Credentials read
- No credential file or variable was opened.
- Credentials sent
- No decoy left the box.
loading it exited 1; many libraries need configuration or a host to load, so this says little either way
Dependencies
2 of 2 installed, as npm would on linux x64 musl.
Show all 2
- @pnpm/exe.linux-x64-musl@12.16.1
- @pnpm/exe.linux-x64@12.16.1
Since the previous version
The install steps are the same as in 12.16.0.
- Compared with
- 12.16.0
From the npm registry manifests of both versions; not part of the signed record.
What it did, compared with the record of 12.16.0
It did the same things as 12.16.0 in the sandbox.
- Level
- quiet
A comparison of the notary's signed records of both versions, made when this page is read; not part of either signature. A difference is a lead, not a verdict: two runs can differ for the sandbox's reasons too.
Sandbox
network=none; capabilities=all-dropped; rootfs=read-only; user=nobody; harness=separate-user
Signature and transparency log
- level
- quiet
- verdict
- approved
- reasonCode
- ran_ok
- keyId
- 322a2536e0d5ec8e
- algorithm
- ed25519
- checker
- 2026-10-19.2
- issuedAt
- 2026-10-29T13:09:11Z
- contentSha256
- ca362a16f2e1c3cfa81d406f3242446179a0e4aea457ba3e9e6c39e6476aba65
- contentSizeBytes
- 1113525 (1.1 MB)
- outputSha256
- 36ef4ea11b230ae8c6dfd3bd5a7198770bfde6878657d482f11ea8a0359eccb8
- log index
- 1058
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 29 Oct 2026, 13:09 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.