bitcoinjs-lib@7.0.2
npm · checked 21 Oct 2026, 23:17 UTC · checker 2026-10-19.2 · log index 947
Record issued 21 Oct 2026
Issued 21 Oct 2026, 23:17 UTC · bitcoinjs-lib@7.0.2 · npm
nothing runs
Nothing of this package's own runs at install.
Nothing of this package's own runs when it is installed. Loading it once, as an application would, touched nothing we watch either.
The trace shows what a step attempted. A quiet trace is evidence, not proof.
The install steps section lists what would have run: nothing. A dependency may still run something; see Dependencies.
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
bitcoinjs-lib 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.
It reached nothing we watch.
- Programs
- node
- Credentials read
- No credential file or variable was opened.
- Credentials sent
- No decoy left the box.
Dependencies
11 of 11 installed, as npm would on linux x64 musl.
Show all 11
- @noble/hashes@1.8.0
- base-x@5.0.1
- bech32@2.0.0
- bip174@3.0.1
- bs58@6.0.0
- bs58check@4.0.0
- uint8array-tools@0.0.10
- uint8array-tools@0.0.10
- uint8array-tools@0.0.9
- valibot@1.5.0
- varuint-bitcoin@2.0.1
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
- nothing_runs
- verdict
- manual_review
- reasonCode
- no_install_steps
- keyId
- 322a2536e0d5ec8e
- algorithm
- ed25519
- checker
- 2026-10-19.2
- issuedAt
- 2026-10-21T23:17:42Z
- contentSha256
- c15fba0dc4d39b37c37cd6e589036b328960e3d7847302df542d5e8667dd8682
- contentSizeBytes
- 114032 (111 KB)
- log index
- 947
Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.
Inclusion proofCheckpointKey list
Issued 21 Oct 2026, 23:17 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.