@bitgo/utxo-lib
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): SLSA provenance attestation via Sigstore confirms legitimate CI/CD publish; established BitGo package with strong ecosystem trust. | ai | |
| dependencies | unvetted-dep:cashaddress | AI (dependencies): Standard Bitcoin Cash address library; expected dep for a multi-coin UTXO lib. | ai | |
| dependencies | unvetted-dep:@bitgo/blake2b | AI (dependencies): BitGo-owned blake2b binding; stable dep for this package. | ai | |
| dependencies | unvetted-dep:@bitgo/secp256k1 | AI (dependencies): BitGo-owned secp256k1 binding; stable dep for this package. | ai | |
| dependencies | unvetted-dep:@brandonblack/musig | AI (dependencies): MuSig crypto library for Taproot; expected dep for a UTXO lib supporting Taproot. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 11.22.1 | 12 / 5 | |
| 11.22.0 | 12 / 5 | |
| 11.17.0 | 12 / 5 | |
| 11.16.1 | 12 / 5 | |
| 11.16.0 | 12 / 5 | |
| 11.15.0 | 12 / 5 | |
| 11.14.0 | 12 / 5 | |
| 11.13.0 | 12 / 5 | |
| 11.11.1 | 17 / 5 | |
| 11.10.0 | 17 / 5 | |
| 11.9.0 | 17 / 5 | |
| 11.8.0 | 17 / 5 | |
| 11.6.3 | 17 / 5 | |
| 11.6.1 | 17 / 5 | |
| 11.6.0 | 17 / 5 |
v11.22.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v11.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.