xrpl
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:build/xrpl-latest-min.js | AI (source-diff): Webpack-minified browser bundle (unpkg/jsdelivr entry), not obfuscation; stable across releases. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Ripple org transition to CI/CD publishing with SLSA attestation; ripple-branded accounts. | ai | |
| provenance | publisher-changed | AI (provenance): Move to GitHub Actions CI/CD publish with Sigstore attestation; provenance improved. | ai | |
| dependencies | unvetted-dep:ripple-keypairs | AI (dependencies): ripple-keypairs is a first-party XRPLF dependency and a long-standing core component of the xrpl.js SDK; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@xrplf/secret-numbers | AI (dependencies): @xrplf/secret-numbers is a first-party XRPLF dependency used for secret number key derivation in xrpl.js; stable false positive for this package. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 10 / 12 | |
| 4.6.0 | 10 / 12 | |
| 4.5.0 | 10 / 12 | |
| 4.4.3 | 10 / 12 | |
| 4.1.0 | 9 / 12 |
v4.5.0
5 findingsAll previous maintainers (intelliot, justinr1234, anissa-ripple, mukulljangid, mvadari, ckniffen, khancode_, pdp2121, shawnxie9999, achowdhry, ckeshavabs) were replaced by new maintainers (vjkhannaripple, mankins, shichengripple001, ripplex-automation). This is a strong signal of a potential package hijack and requires careful review.
This 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.
This version was published by a different npm account than previous versions on 2025-12-16. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.3
5 findingsAll previous maintainers (intelliot, justinr1234, anissa-ripple, mukulljangid, mvadari, ckniffen, khancode_, pdp2121, shawnxie9999, achowdhry, ckeshavabs) were replaced by new maintainers (vjkhannaripple, mankins, shichengripple001, ripplex-automation). This is a strong signal of a potential package hijack and requires careful review.
This 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.
This version was published by a different npm account than previous versions on 2025-11-07. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.