@solana-program/token
JavaScript client for the Token program
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/src/index.mjs | AI (source-diff): tsup-bundled readable ESM output, not obfuscation; stable build artifact. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Generated codec source files from Solana program client; normal for this package. | ai | |
| 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 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.15.0 | 1 / 14 | |
| 0.14.0 | 1 / 14 | |
| 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 | |
| 0.5.1 | 0 / 14 | |
| 0.5.0 | 0 / 14 | |
| 0.4.1 | 0 / 14 | |
| 0.4.0 | 0 / 14 | |
| 0.3.3 | 0 / 14 | |
| 0.3.2 | 0 / 15 | |
| 0.3.1 | 0 / 15 | |
| 0.3.0 | 0 / 15 | |
| 0.2.1 | 0 / 16 | |
| 0.2.0 | 0 / 16 | |
| 0.1.4 | 0 / 15 | |
| 0.1.3 | 0 / 15 | |
| 0.1.2 | 0 / 15 | |
| 0.1.1 | 0 / 15 | |
| 0.1.0 | 0 / 15 |
v0.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-03-03. This could indicate a legitimate maintainer transition or an account compromise.
v0.5.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-03-03. This could indicate a legitimate maintainer transition or an account compromise.
v0.4.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.