@solana-program/compute-budget
JavaScript client for the Compute Budget 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@solana/accounts | AI (phantom-deps): Likely used via bundled types/re-exports; official Solana monorepo package, not malicious. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publishing with SLSA attestation; legitimate automation. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): 127.0.0.1:8899 in JSDoc example comment for local Solana validator; not a real network call. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.17.0 | 0 / 13 | |
| 0.16.0 | 0 / 13 | |
| 0.15.0 | 0 / 12 | |
| 0.14.0 | 0 / 12 | |
| 0.13.0 | 0 / 12 | |
| 0.12.0 | 0 / 12 | |
| 0.11.0 | 0 / 12 | |
| 0.10.0 | 0 / 12 | |
| 0.9.0 | 0 / 12 | |
| 0.8.0 | 0 / 12 | |
| 0.7.0 | 0 / 13 | |
| 0.6.1 | 0 / 13 | |
| 0.6.0 | 0 / 13 | |
| 0.5.4 | 0 / 13 | |
| 0.5.3 | 0 / 14 | |
| 0.5.2 | 0 / 14 | |
| 0.5.1 | 0 / 14 | |
| 0.5.0 | 0 / 15 | |
| 0.4.1 | 0 / 15 | |
| 0.4.0 | 0 / 15 | |
| 0.3.2 | 0 / 14 | |
| 0.3.1 | 0 / 14 | |
| 0.3.0 | 0 / 14 | |
| 0.2.0 | 6 / 14 | |
| 0.1.1 | 6 / 18 | |
| 0.1.0 | 6 / 18 |
v0.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.0
2 findingsPackage 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.6.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.