@pancakeswap/multicall
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has clean track record (8 approved); minor version bump with no material changes makes takeover scenario unlikely. | ai | |
| dependencies | unvetted-dep:@pancakeswap/sdk | AI (dependencies): First-party sibling package within the @pancakeswap org; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): PancakeSwap packages consistently lack Sigstore provenance; stable false positive for this org. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 3.8.1 | 3 / 3 | |
| 3.8.0 | 3 / 3 | |
| 3.7.4 | 3 / 3 | |
| 3.7.3 | 3 / 3 | |
| 3.7.2 | 3 / 3 | |
| 3.7.1 | 3 / 3 | |
| 3.7.0 | 3 / 3 | |
| 3.6.4 | 3 / 3 | |
| 3.6.3 | 3 / 3 | |
| 3.6.2 | 3 / 3 | |
| 3.6.1 | 3 / 3 | |
| 3.6.0 | 3 / 3 | |
| 3.5.10 | 3 / 3 | |
| 3.5.9 | 3 / 3 | |
| 3.5.8 | 3 / 3 | |
| 3.5.7 | 3 / 3 | |
| 3.5.6 | 3 / 3 | |
| 3.5.5 | 3 / 3 | |
| 3.5.4 | 3 / 3 | |
| 3.5.3 | 3 / 3 | |
| 3.5.2 | 3 / 3 |
v3.8.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.
v3.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.9
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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.8
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.
v3.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.