@caravan/bitcoin
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Unchained Capital package; missing provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): Buffer is declared for browser bundler compatibility, not directly imported — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a known implicit Babel polyfill dependency; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped Babel runtime loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/polyfill | AI (phantom-deps): Babel polyfill loaded by convention; stable false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.4.5 | 11 / 19 | |
| 0.4.3 | 11 / 19 | |
| 0.4.2 | 11 / 19 | |
| 0.4.1 | 11 / 19 | |
| 0.4.0 | 11 / 19 | |
| 0.3.4 | 11 / 19 | |
| 0.3.3 | 11 / 19 |
v0.4.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.