@solana/spl-token-metadata
SPL Token Metadata Interface JS API
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Trusted first-party Solana package; publish-env metadata gap, no behavior change. | ai | |
| provenance | no-provenance | AI (provenance): Legacy manual publish for established first-party package; not a risk. | ai | |
| phantom-deps | phantom-dep:@solana/codecs-core | AI (phantom-deps): Same-org scope, used transitively/via re-export; stable FP. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.1.6 | 1 / 17 | |
| 0.1.5 | 2 / 16 | |
| 0.1.4 | 2 / 19 | |
| 0.1.3 | 2 / 19 | |
| 0.1.2 | 6 / 19 | |
| 0.1.1 | 6 / 19 | |
| 0.1.0 | 6 / 20 | |
| 0.0.1 | 6 / 20 |
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (steveluscher) than the most recent previously approved version (buffalojoec) on 2024-04-19, but steveluscher is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (steveluscher) than the most recent previously approved version (buffalojoec) on 2024-04-18, but steveluscher is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.1.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: buffalojoec.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.