ripple-binary-codec
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Transition to GitHub Actions CI/CD; SLSA provenance present. Stable for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Org-level CI publish transition for XRPLF monorepo; not a takeover signal. | ai | |
| dependencies | unvetted-dep:@xrplf/isomorphic | AI (dependencies): @xrplf/isomorphic is a first-party XRPLF package; a legitimate and expected dependency for this XRP Ledger Foundation codec library. | ai | |
| dependencies | unvetted-dep:ripple-address-codec | AI (dependencies): ripple-address-codec is a first-party XRPLF package; a legitimate and expected dependency for this XRP Ledger codec library. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.8.0 | 3 / 0 | |
| 2.7.0 | 3 / 0 | |
| 2.6.0 | 3 / 0 | |
| 2.5.1 | 3 / 0 | |
| 2.5.0 | 3 / 0 | |
| 2.4.1 | 3 / 0 | |
| 2.4.0 | 3 / 0 |
v2.8.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.