@pancakeswap/v3-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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Publisher chefjackson has 42 approved packages; stale takeover pattern ruled out. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine maintainer rotation within org, no takeover indicators. | ai | |
| provenance | publisher-changed-stale | AI (provenance): 733d stable on npm without removal, inconsistent with compromise. | ai | |
| phantom-deps | phantom-dep:decimal.js-light | AI (phantom-deps): Declared runtime dep used in built output; phantom-dep heuristic fires on bundled SDK. | ai | |
| phantom-deps | phantom-dep:big.js | AI (phantom-deps): Declared runtime dep used in built output; phantom-dep heuristic fires on bundled SDK. | ai | |
| phantom-deps | phantom-dep:@pancakeswap/tokens | AI (phantom-deps): Same-org dep declared in package.json; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@uniswap/v3-staker | AI (phantom-deps): Declared runtime dep used in built output; phantom-dep heuristic fires on bundled SDK. | ai | |
| phantom-deps | phantom-dep:toformat | AI (phantom-deps): Declared runtime dep used in built output; phantom-dep heuristic fires on bundled SDK. | ai | |
| phantom-deps | phantom-dep:tiny-warning | AI (phantom-deps): Declared runtime dep used in built output; phantom-dep heuristic fires on bundled SDK. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 3.10.1 | 9 / 2 | |
| 3.10.0 | 9 / 2 | |
| 3.9.4 | 9 / 2 | |
| 3.9.3 | 9 / 2 | |
| 3.9.2 | 9 / 2 | |
| 3.9.1 | 9 / 2 | |
| 3.9.0 | 9 / 2 | |
| 3.8.13 | 9 / 2 | |
| 3.8.12 | 9 / 2 | |
| 3.8.11 | 9 / 2 | |
| 3.8.10 | 9 / 2 | |
| 3.8.9 | 9 / 2 | |
| 3.8.8 | 9 / 2 | |
| 3.8.7 | 9 / 2 | |
| 3.8.6 | 9 / 2 | |
| 3.8.5 | 9 / 2 | |
| 3.8.4 | 9 / 2 | |
| 3.8.3 | 9 / 2 | |
| 3.1.1 | 10 / 4 |
v3.10.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.
v3.9.3
2 findingsThis version was published by a different npm account (chefjackson) than the most recent previously approved version (chef-jojo) on 2025-04-29. It has since remained available on npm for 445 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.2
2 findingsThis version was published by a different npm account (chefjackson) than the most recent previously approved version (chef-jojo) on 2025-04-28. It has since remained available on npm for 446 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.1
2 findingsThis version was published by a different npm account (chefjackson) than the most recent previously approved version (chef-jojo) on 2025-04-25. It has since remained available on npm for 449 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
2 findingsThis version was published by a different npm account (chefjackson) than the most recent previously approved version (chef-jojo) on 2025-02-25. It has since remained available on npm for 508 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.13
2 findingsThis version was published by a different npm account (chefjackson) than the most recent previously approved version (chef-jojo) on 2024-12-04. It has since remained available on npm for 591 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.12
2 findingsThis version was published by a different npm account (chefjackson) than the most recent previously approved version (chef-jojo) on 2024-10-29. It has since remained available on npm for 627 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.11
2 findingsThis version was published by a different npm account (chefjackson) than the most recent previously approved version (chef-jojo) on 2024-07-22. It has since remained available on npm for 726 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.10
2 findingsThis version was published by a different npm account (chefjackson) than the most recent previously approved version (chef-jojo) on 2024-07-15. It has since remained available on npm for 733 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.9
2 findingsThis version was published by a different npm account (chefjackson) than the most recent previously approved version (chef-jojo) on 2024-07-15. It has since remained available on npm for 733 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.