stellar-sdk
1
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
stellar-npm-cistellar-npmbarteknquietbitsjaceknfnando_sdfcassiomgpiyalbasu
Keywords
stellar
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): stellar-sdk handles Stellar/XDR protocol data which is inherently base64-encoded (transactions, auth entries, envelopes). Base64 decoding is a core, legitimate operation throughout this blockchain SDK. | ai | |
| provenance | no-provenance | AI (provenance): Established Stellar Foundation SDK published via dedicated CI account; lack of Sigstore provenance is not a meaningful risk signal for this well-known package. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 13.3.0 | 8 / 68 |
v13.3.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.