← Home

ripple-binary-codec

npm Repository Homepage
11
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

shichengripple001ripplex-automation

Keywords

ripplexrpxrp ledgerxrpl

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate maintainer transition on XRPLF monorepo; no material diff. ai
maintainer-change maintainer-added AI (maintainer-change): Same handoff signal; benign for this established package. ai
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 11 of 11)

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
2.3.0 3 / 0
2.2.0 3 / 0
2.1.0 3 / 0
2.0.0 3 / 0

v2.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.0

2 findings
HIGH Publisher changed: khancode_ → ckeshavabs (on 2024-12-23) provenance

This version was published by a different npm account than previous versions on 2024-12-23. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.