@statoscope/webpack-stats-extension-compressed
Webpack adapter for @statoscope/stats-extension-compressed
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Publish metadata quirk, no behavioral change; stable maintainer track record. | ai | |
| provenance | no-provenance | AI (provenance): Lack of provenance attestation alone isn't malicious for this trusted package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Scoped monorepo utility; sparse README and no keywords are typical for internal tooling packages. | ai | |
| phantom-deps | phantom-dep:@types/webpack | AI (phantom-deps): @types/webpack is a type-only dep used at compile time; not imported at runtime by convention. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 5.29.0 | 4 / 0 | |
| 5.28.3 | 4 / 0 | |
| 5.28.2 | 4 / 0 | |
| 5.28.1 | 4 / 0 | |
| 5.28.0 | 3 / 1 | |
| 5.27.0 | 3 / 1 | |
| 5.26.2 | 3 / 1 | |
| 5.25.1 | 3 / 1 | |
| 5.25.0 | 3 / 1 | |
| 5.24.0 | 3 / 1 | |
| 5.23.0 | 3 / 1 | |
| 5.22.0 | 3 / 1 | |
| 5.20.1 | 3 / 1 | |
| 5.20.0 | 4 / 0 | |
| 5.19.3 | 4 / 0 | |
| 5.19.1 | 4 / 0 | |
| 5.19.0 | 4 / 0 | |
| 5.18.0 | 4 / 0 | |
| 5.17.0 | 4 / 0 | |
| 5.14.1 | 4 / 0 | |
| 5.14.0 | 4 / 0 | |
| 5.13.1 | 4 / 0 | |
| 5.13.0 | 4 / 0 | |
| 5.9.0 | 2 / 1 | |
| 5.7.1 | 2 / 1 | |
| 5.7.0 | 2 / 1 | |
| 5.6.1 | 1 / 2 | |
| 5.6.0 | 1 / 2 | |
| 5.5.1 | 1 / 2 | |
| 5.4.2 | 1 / 2 | |
| 5.4.0 | 1 / 2 | |
| 5.3.1 | 1 / 2 | |
| 5.3.0 | 1 / 2 |
v5.28.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.28.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: smelukov.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.