@loadable/webpack-plugin
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 |
|---|---|---|---|---|
| provenance | publisher-changed-stale | AI (provenance): Long-stale publisher change, not a fresh takeover indicator. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same stale maintainer change, consistent historical publisher. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): make-dir replaces mkdirp, a benign well-known utility swap. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 5.15.2 | 1 / 0 | |
| 5.15.1 | 1 / 0 | |
| 5.15.0 | 1 / 0 | |
| 5.14.2 | 1 / 0 | |
| 5.14.0 | 1 / 0 | |
| 5.13.0 | 1 / 0 | |
| 5.12.0 | 1 / 0 | |
| 5.7.1 | 1 / 0 | |
| 5.7.0 | 0 / 0 | |
| 5.5.0 | 0 / 0 | |
| 5.4.0 | 0 / 0 | |
| 5.2.2 | 0 / 0 | |
| 5.2.1 | 0 / 0 | |
| 5.2.0 | 0 / 0 | |
| 5.0.2 | 0 / 0 | |
| 5.0.1 | 0 / 0 | |
| 5.0.0 | 0 / 0 |
v5.15.1
2 findingsThis version was published by a different npm account (kashey) than the most recent previously approved version (neoziro) on 2021-08-17. It has since remained available on npm for 1801 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.0
2 findingsThis version was published by a different npm account (kashey) than the most recent previously approved version (neoziro) on 2021-05-08. It has since remained available on npm for 1903 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.2
2 findingsThis version was published by a different npm account (kashey) than the most recent previously approved version (neoziro) on 2021-01-31. It has since remained available on npm for 1999 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.0
2 findingsThis version was published by a different npm account (kashey) than the most recent previously approved version (neoziro) on 2020-10-20. It has since remained available on npm for 2102 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
2 findingsThis version was published by a different npm account (kashey) than the most recent previously approved version (neoziro) on 2020-06-29. It has since remained available on npm for 2215 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package 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.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.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.