@pancakeswap/gauges
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@pancakeswap/tokens | AI (phantom-deps): Declared in dependencies; used transitively by @pancakeswap/v3-sdk. False positive for monorepo packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo package; missing metadata is normal for scoped utility libraries without public-facing docs. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.0.12 | 4 / 4 | |
| 2.0.11 | 4 / 6 | |
| 2.0.10 | 4 / 6 | |
| 2.0.9 | 4 / 6 | |
| 2.0.8 | 4 / 6 | |
| 2.0.7 | 4 / 6 | |
| 2.0.6 | 4 / 6 | |
| 2.0.5 | 4 / 5 | |
| 2.0.4 | 4 / 5 | |
| 2.0.3 | 4 / 5 | |
| 2.0.2 | 4 / 5 | |
| 2.0.1 | 4 / 5 | |
| 2.0.0 | 4 / 5 |
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.