@solana-program/token
JavaScript client for the Token program
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): joncinque is a known Solana developer with strong track record (7 approved packages). Transition from solana-devs org account to individual maintainer is a legitimate and common open-source pattern. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @solana-program/system is a sibling package in the same GitHub org; Token program depending on System program is architecturally expected in Solana. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.13.0 | 1 / 14 | |
| 0.12.0 | 1 / 14 | |
| 0.11.0 | 1 / 14 | |
| 0.10.0 | 0 / 14 | |
| 0.9.0 | 0 / 14 | |
| 0.8.1 | 0 / 14 | |
| 0.8.0 | 0 / 14 | |
| 0.7.0 | 0 / 14 | |
| 0.6.0 | 0 / 14 |
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.