static-site-generator-webpack-plugin
Minimal, unopinionated static site generator powered by webpack
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:coverage/lcov-report/prettify.js | AI (source-diff): This is Google Code Prettify, a minified syntax highlighter auto-generated by Istanbul in LCOV HTML coverage reports. It is not a runtime file and poses no security risk. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is entirely explained by the inclusion of Istanbul-generated coverage report artifacts (lcov-report directory), not injected payloads. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from markdalgleish to jahredhope occurred in 2018 (~6 years ago); jahredhope has a clean track record (3 approved packages), repo URL unchanged. Transition is stable and legitimate. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy aligns with the 2018 maintainer transition period. Package is well-established with 19.4k weekly downloads and no malicious indicators. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 3.4.2 | 5 / 15 | |
| 3.4.1 | 5 / 14 | |
| 3.4.0 | 5 / 14 | |
| 3.3.0 | 3 / 14 | |
| 3.2.0 | 3 / 14 | |
| 3.1.2 | 3 / 14 | |
| 3.1.1 | 3 / 14 | |
| 3.1.0 | 3 / 14 | |
| 3.0.0 | 3 / 14 | |
| 2.1.1 | 2 / 13 | |
| 2.1.0 | 2 / 13 | |
| 2.0.1 | 2 / 12 | |
| 2.0.0 | 2 / 9 | |
| 1.3.0 | 2 / 0 | |
| 1.2.1 | 2 / 0 | |
| 1.2.0 | 2 / 0 | |
| 1.1.2 | 2 / 0 | |
| 1.1.1 | 2 / 0 | |
| 1.1.0 | 2 / 0 | |
| 1.0.1 | 2 / 0 | |
| 1.0.0 | 2 / 0 |
v3.4.2
2 findingsThis version was published by a different npm account than previous versions on 2018-11-19. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.