@pancakeswap/sdk
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Long-standing publisher transition already vetted across 21 prior approved versions. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Publisher chefjackson has established track record (21 approved pkgs), transition predates this version. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with legitimate maintainer handoff, no malicious behavior evident. | ai | |
| phantom-deps | phantom-dep:tiny-warning | AI (phantom-deps): tiny-warning is a declared runtime dep used in compiled output; stable FP. | ai | |
| phantom-deps | phantom-dep:viem | AI (phantom-deps): viem is a declared runtime dep used in compiled output; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:decimal.js-light | AI (phantom-deps): decimal.js-light is a declared runtime dep used in compiled output; stable FP. | ai | |
| phantom-deps | phantom-dep:big.js | AI (phantom-deps): big.js is a declared runtime dep used in compiled output; stable FP. | ai | |
| phantom-deps | phantom-dep:toformat | AI (phantom-deps): toformat is a declared runtime dep used in compiled output; stable FP. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 5.9.1 | 11 / 2 | |
| 5.9.0 | 11 / 2 | |
| 5.8.18 | 11 / 2 | |
| 5.8.17 | 11 / 2 | |
| 5.8.16 | 11 / 2 | |
| 5.8.15 | 10 / 2 | |
| 5.8.14 | 10 / 2 | |
| 5.8.13 | 10 / 2 | |
| 5.8.12 | 10 / 2 | |
| 5.8.11 | 10 / 2 | |
| 5.8.10 | 10 / 2 | |
| 5.8.9 | 10 / 2 | |
| 5.8.8 | 10 / 2 | |
| 5.8.7 | 10 / 2 | |
| 5.8.6 | 10 / 2 | |
| 5.8.5 | 10 / 2 | |
| 5.8.4 | 10 / 2 | |
| 5.8.3 | 10 / 2 | |
| 5.8.2 | 8 / 2 | |
| 5.8.1 | 8 / 2 | |
| 5.8.0 | 8 / 2 | |
| 5.7.7 | 8 / 2 | |
| 5.7.6 | 8 / 2 | |
| 5.7.5 | 8 / 2 | |
| 5.7.4 | 8 / 2 | |
| 5.7.3 | 8 / 2 | |
| 5.7.2 | 8 / 2 | |
| 5.7.1 | 8 / 2 | |
| 5.7.0 | 8 / 2 | |
| 5.6.0 | 8 / 2 | |
| 5.5.0 | 8 / 2 | |
| 5.4.2 | 8 / 2 | |
| 5.4.1 | 7 / 2 | |
| 5.4.0 | 7 / 2 | |
| 5.3.0 | 7 / 2 | |
| 5.2.1 | 7 / 2 | |
| 5.2.0 | 7 / 2 | |
| 5.1.0 | 7 / 2 | |
| 5.0.0 | 7 / 4 |
v5.9.1
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 (chef-jerry) than the most recent previously approved version (chefjackson) on 2026-07-03, but chef-jerry 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.
v5.8.12
2 findingsThis version was published by a different npm account than previous versions on 2025-04-25. 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.
v5.8.11
2 findingsThis version was published by a different npm account than previous versions on 2025-02-25. 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.
v5.8.10
2 findingsThis version was published by a different npm account than previous versions on 2024-12-04. 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.
v5.8.9
2 findingsThis version was published by a different npm account than previous versions on 2024-10-29. 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.
v5.8.8
2 findingsThis version was published by a different npm account than previous versions on 2024-07-22. 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.
v5.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.