@easylayer/bitcoin
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:rxjs | AI (phantom-deps): rxjs is a standard NestJS peer/implicit dep; not directly imported but legitimately used. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash commonly used via transitive or config-level references in NestJS projects. | ai | |
| phantom-deps | phantom-dep:@nestjs/swagger | AI (phantom-deps): NestJS swagger is a peer dep for decorator metadata; not always directly imported. | ai | |
| phantom-deps | phantom-dep:@noble/secp256k1 | AI (phantom-deps): Crypto lib used indirectly via bitcoinjs-lib/bip32 ecosystem; phantom heuristic fires but dep is legitimate. | ai | |
| phantom-deps | phantom-dep:reflect-metadata | AI (phantom-deps): Known NestJS runtime implicit dep; always declared but rarely directly imported. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.2.1 | 19 / 19 | |
| 1.2.0 | 19 / 19 | |
| 1.1.1 | 20 / 14 | |
| 1.0.4 | 20 / 14 | |
| 1.0.3 | 20 / 14 | |
| 1.0.2 | 20 / 14 | |
| 1.0.0 | 19 / 15 |
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.