@solana/spl-token
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
solana-devs
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@solana/spl-token-group | AI (dependencies): First-party Solana Labs sub-package from the same org; expected dependency for SPL token ecosystem. | ai | |
| dependencies | unvetted-dep:@solana/spl-token-metadata | AI (dependencies): First-party Solana Labs sub-package from the same org; expected dependency for SPL token ecosystem. | ai | |
| dependencies | unvetted-dep:@solana/buffer-layout-utils | AI (dependencies): First-party Solana Labs utility package; stable dependency used across the SPL ecosystem. | ai | |
| phantom-deps | phantom-dep:buffer | AI (phantom-deps): buffer is a declared runtime dep used as a browser polyfill; common pattern for isomorphic packages, not a security concern. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.4.14 | 5 / 25 |
v0.4.14
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.