@statoscope/webpack-model
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:jora | AI (dependencies): Known jora query library, long-standing dep, no malicious behavior. | ai | |
| phantom-deps | phantom-dep:@types/md5 | AI (phantom-deps): @types/md5 is a TypeScript type declaration; loaded by convention, not direct import. | ai | |
| phantom-deps | phantom-dep:@types/webpack | AI (phantom-deps): @types/webpack is a TypeScript type declaration; loaded by convention, not direct import. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate monorepo sub-package; sparse README and no keywords are typical for internal tooling packages. | ai |
Versions (showing 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 5.29.0 | 11 / 1 | |
| 5.28.3 | 11 / 1 | |
| 5.28.2 | 11 / 1 | |
| 5.28.1 | 11 / 1 | |
| 5.28.0 | 9 / 3 | |
| 5.27.0 | 9 / 3 | |
| 5.26.2 | 9 / 3 | |
| 5.25.1 | 9 / 3 | |
| 5.25.0 | 9 / 3 | |
| 5.24.0 | 9 / 3 | |
| 5.23.0 | 10 / 3 | |
| 5.22.0 | 10 / 3 | |
| 5.20.1 | 10 / 3 | |
| 5.20.0 | 12 / 1 | |
| 5.19.3 | 12 / 1 | |
| 5.19.1 | 12 / 1 | |
| 5.19.0 | 12 / 1 | |
| 5.18.0 | 12 / 1 | |
| 5.17.0 | 12 / 1 | |
| 5.14.1 | 12 / 1 | |
| 5.14.0 | 12 / 1 | |
| 5.13.1 | 12 / 1 | |
| 5.13.0 | 12 / 1 | |
| 5.12.1 | 10 / 2 | |
| 5.12.0 | 10 / 2 | |
| 5.11.0 | 10 / 2 | |
| 5.9.0 | 10 / 2 | |
| 5.8.0 | 9 / 2 | |
| 5.7.3 | 9 / 2 | |
| 5.7.1 | 9 / 2 | |
| 5.7.0 | 9 / 2 | |
| 5.6.2 | 8 / 2 | |
| 5.6.1 | 8 / 2 | |
| 5.6.0 | 8 / 2 | |
| 5.5.1 | 8 / 2 | |
| 5.4.2 | 8 / 2 | |
| 5.4.1 | 8 / 2 | |
| 5.4.0 | 8 / 2 | |
| 5.3.1 | 8 / 2 | |
| 5.3.0 | 8 / 2 | |
| 5.2.0 | 3 / 2 | |
| 5.1.0 | 3 / 1 | |
| 5.0.0 | 3 / 0 |
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.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.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.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.3
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.