plyr
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): core-js is a declared runtime dep used as a polyfill; phantom-dep heuristic fires because it's bundled rather than directly imported. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.8.4 | 5 / 55 | |
| 3.7.2 | 5 / 50 | |
| 3.7.1 | 5 / 49 | |
| 3.7.0 | 5 / 49 | |
| 3.6.12 | 5 / 48 | |
| 3.6.11 | 5 / 48 |
v3.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.