@ewizardjs/dev-builder
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:vue-template-compiler | AI (dependencies): vue-template-compiler is a well-known Vue 2 ecosystem package; stable false positive for this build-tool package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require of BLOCKS_MANIFEST env var is a documented plugin/manifest loader pattern for this build tool; stable across versions. | ai | |
| phantom-deps | phantom-dep:connect-history-api-fallback | AI (phantom-deps): connect-history-api-fallback is a declared runtime dep used in webpack-dev-server config; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 5.5.0 | 30 / 21 | |
| 5.4.0 | 30 / 21 | |
| 5.3.0 | 30 / 21 | |
| 5.2.4 | 30 / 21 | |
| 5.2.3 | 30 / 21 | |
| 5.2.1 | 30 / 21 | |
| 5.2.0 | 30 / 21 | |
| 4.24.0 | 30 / 21 | |
| 4.23.0 | 30 / 21 |
v5.5.0
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.1
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.
v4.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.