@pancakeswap/permit2-sdk
An sdk for interacting with permit2.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@pancakeswap/sdk | AI (dependencies): Internal PancakeSwap ecosystem dependency; stable false positive for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has clean track record; no material changes from prior version; consistent with infrequent but legitimate maintenance cadence. | ai | |
| provenance | no-provenance | AI (provenance): PancakeSwap monorepo packages consistently lack Sigstore provenance; stable false positive for this package family. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 1.2.1 | 4 / 2 | |
| 1.2.0 | 4 / 2 | |
| 1.1.7 | 4 / 2 | |
| 1.1.6 | 4 / 2 | |
| 1.1.5 | 4 / 2 | |
| 1.1.4 | 4 / 2 | |
| 1.1.3 | 4 / 2 | |
| 1.1.2 | 4 / 2 | |
| 1.1.1 | 4 / 2 | |
| 1.1.0 | 4 / 2 | |
| 1.0.12 | 4 / 2 | |
| 1.0.11 | 4 / 2 | |
| 1.0.10 | 4 / 2 | |
| 1.0.9 | 4 / 2 | |
| 1.0.8 | 4 / 2 | |
| 1.0.7 | 4 / 2 | |
| 1.0.6 | 4 / 2 | |
| 1.0.5 | 4 / 2 | |
| 1.0.4 | 4 / 2 |
v1.2.1
2 findings[Accepted risk] Package 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.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.