← Home

@pancakeswap/token-lists

npm
8
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
provenance publisher-changed-stale AI (provenance): Stable on npm 726d, consistent with legitimate handoff not takeover. ai
bogus-package bogus-package AI (bogus-package): Monorepo sub-package metadata sparsity is typical, not spam. ai
maintainer-change maintainer-added AI (maintainer-change): Monorepo team rotation; publisher has strong track record, no compromise indicators. ai

Versions (showing 8 of 8)

Version Deps Published
0.1.0 3 / 8
0.0.17 3 / 7
0.0.16 3 / 7
0.0.15 3 / 7
0.0.14 3 / 7
0.0.13 3 / 7
0.0.12 3 / 7
0.0.8 3 / 7

v0.1.0

1 finding
LOW No provenance attestation provenance

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

v0.0.17

1 finding
LOW No provenance attestation provenance

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

v0.0.16

1 finding
LOW No provenance attestation provenance

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

v0.0.15

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

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

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

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.