← Home

@pancakeswap/tokens

npm
26
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

pancakeswapadminchefjacksonchef-jerry

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): New dep is official first-party @pancakeswap/chains sibling package. ai
provenance publisher-changed-stale AI (provenance): Long-stale publisher change with no unpublish, consistent with legitimate maintainer rotation. ai
maintainer-change maintainer-added AI (maintainer-change): Known org-internal maintainer rotation, publisher has strong track record. ai
maintainer-change maintainer-removed AI (maintainer-change): Consistent with normal team rotation, not takeover. ai
publish-pattern dormant-publish AI (publish-pattern): Monorepo package publishes in batches; publisher has clean long track record. ai
semgrep semgrep:shady-links-tlds AI (semgrep): Fires on token homepage URLs embedded in ERC20Token definitions; not C2/exfiltration — stable false positive for this token-list package. ai

Versions (showing 26 of 26)

Version Deps Published
0.9.0 3 / 3
0.8.0 3 / 3
0.7.10 3 / 3
0.7.9 3 / 3
0.7.6 3 / 2
0.7.4 3 / 2
0.7.3 3 / 2
0.7.2 3 / 2
0.7.1 3 / 2
0.7.0 3 / 2
0.6.29 3 / 2
0.6.28 3 / 2
0.6.27 3 / 2
0.6.26 3 / 2
0.6.25 3 / 2
0.6.24 3 / 2
0.6.23 3 / 2
0.6.22 3 / 2
0.6.21 3 / 2
0.6.20 3 / 2
0.6.19 3 / 2
0.6.18 3 / 2
0.6.17 3 / 2
0.6.16 3 / 2
0.6.15 3 / 2
0.1.6 2 / 1

v0.9.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: chefjackson → chef-jerry (on 2026-07-03, known maintainer) provenance

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.

v0.7.4

2 findings
MEDIUM Publisher changed: chef-jojo → chefjackson (on 2025-04-29, unremoved on npm for 445d) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.3

2 findings
MEDIUM Publisher changed: chef-jojo → chefjackson (on 2025-04-28, unremoved on npm for 446d) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.2

2 findings
MEDIUM Publisher changed: chef-jojo → chefjackson (on 2025-04-25, unremoved on npm for 449d) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.1

2 findings
MEDIUM Publisher changed: chef-jojo → chefjackson (on 2025-04-18, unremoved on npm for 456d) provenance

This version was published by a different npm account (chefjackson) than the most recent previously approved version (chef-jojo) on 2025-04-18. It has since remained available on npm for 456 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

2 findings
MEDIUM Publisher changed: chef-jojo → chefjackson (on 2025-02-25, unremoved on npm for 508d) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.29

2 findings
MEDIUM Publisher changed: chef-jojo → chefjackson (on 2024-12-04, unremoved on npm for 591d) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.28

2 findings
MEDIUM Publisher changed: chef-jojo → chefjackson (on 2024-10-29, unremoved on npm for 627d) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.27

2 findings
MEDIUM Publisher changed: chef-jojo → chefjackson (on 2024-09-29, unremoved on npm for 657d) provenance

This version was published by a different npm account (chefjackson) than the most recent previously approved version (chef-jojo) on 2024-09-29. It has since remained available on npm for 657 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.26

2 findings
MEDIUM Publisher changed: chef-jojo → chefjackson (on 2024-09-19, unremoved on npm for 667d) provenance

This version was published by a different npm account (chefjackson) than the most recent previously approved version (chef-jojo) on 2024-09-19. It has since remained available on npm for 667 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.25

2 findings
MEDIUM Publisher changed: chef-jojo → chefjackson (on 2024-08-31, unremoved on npm for 686d) provenance

This version was published by a different npm account (chefjackson) than the most recent previously approved version (chef-jojo) on 2024-08-31. It has since remained available on npm for 686 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.24

2 findings
MEDIUM Publisher changed: chef-jojo → chefjackson (on 2024-08-21, unremoved on npm for 696d) provenance

This version was published by a different npm account (chefjackson) than the most recent previously approved version (chef-jojo) on 2024-08-21. It has since remained available on npm for 696 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.23

2 findings
MEDIUM Publisher changed: chef-jojo → chefjackson (on 2024-07-22, unremoved on npm for 726d) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.22

2 findings
MEDIUM Publisher changed: chef-jojo → chefjackson (on 2024-07-15, unremoved on npm for 733d) provenance

This 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.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.21

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.20

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.