@evjs/bundler-webpack
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:swc-loader | AI (phantom-deps): Webpack loader; used via config, not direct import. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:html-webpack-plugin | AI (phantom-deps): Webpack plugin; used via config, not direct import. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@evjs/manifest | AI (phantom-deps): Same-org scoped dep; used indirectly. Stable for this package. | ai | |
| phantom-deps | phantom-dep:@swc/core | AI (phantom-deps): Webpack loader; used via config, not direct import. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:webpack-dev-server | AI (phantom-deps): Webpack plugin; used via config, not direct import. Stable pattern for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): memfs is a legitimate, well-established in-memory FS package; natural fit for a webpack bundler adapter. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from human publisher to GitHub Actions CI is expected and backed by SLSA provenance attestation. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 0.2.15 | 9 / 5 | |
| 0.2.14 | 9 / 5 | |
| 0.2.13 | 9 / 5 | |
| 0.2.12 | 9 / 5 | |
| 0.2.11 | 9 / 5 | |
| 0.2.10 | 9 / 5 | |
| 0.2.9 | 9 / 5 | |
| 0.2.8 | 9 / 5 | |
| 0.2.7 | 9 / 5 | |
| 0.2.6 | 9 / 5 | |
| 0.2.5 | 9 / 5 | |
| 0.2.4 | 9 / 5 | |
| 0.2.3 | 9 / 5 | |
| 0.2.2 | 8 / 5 | |
| 0.2.1 | 8 / 5 | |
| 0.2.0 | 8 / 5 | |
| 0.0.26 | 9 / 2 | |
| 0.0.25 | 9 / 2 | |
| 0.0.24 | 9 / 2 | |
| 0.0.23 | 9 / 2 | |
| 0.0.22 | 9 / 2 | |
| 0.0.21 | 9 / 2 | |
| 0.0.20 | 9 / 2 | |
| 0.0.19 | 9 / 2 | |
| 0.0.18 | 8 / 2 | |
| 0.0.17 | 9 / 2 | |
| 0.0.16 | 9 / 2 | |
| 0.0.15 | 9 / 2 | |
| 0.0.14 | 9 / 2 | |
| 0.0.13 | 9 / 2 | |
| 0.0.12 | 9 / 2 | |
| 0.0.11 | 9 / 2 | |
| 0.0.10 | 9 / 2 | |
| 0.0.9 | 9 / 2 | |
| 0.0.8 | 9 / 2 | |
| 0.0.7 | 9 / 2 |
v0.2.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.3
2 findingsThis version was published by a different npm account than previous versions on 2026-06-30. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.