webpack-sources
Source code handling classes for 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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions with SLSA attestation — this reflects the webpack org's migration to automated CI/CD publishing, not a compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): avivkeller is a known webpack contributor; addition is consistent with legitimate webpack org maintainer transitions. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 3.5.0 | 0 / 15 | |
| 3.4.1 | 0 / 15 | |
| 3.4.0 | 0 / 15 | |
| 3.3.4 | 0 / 11 | |
| 3.3.3 | 0 / 24 | |
| 3.3.2 | 0 / 16 | |
| 3.3.1 | 0 / 16 | |
| 3.3.0 | 0 / 16 | |
| 3.2.3 | 0 / 13 | |
| 3.2.2 | 0 / 13 | |
| 3.2.1 | 0 / 13 | |
| 3.2.0 | 0 / 13 | |
| 3.1.2 | 0 / 13 | |
| 3.1.1 | 0 / 13 | |
| 3.1.0 | 0 / 13 | |
| 3.0.4 | 0 / 13 | |
| 3.0.3 | 0 / 13 | |
| 3.0.2 | 0 / 13 | |
| 3.0.1 | 0 / 13 | |
| 3.0.0 | 0 / 13 | |
| 2.3.1 | 2 / 12 | |
| 2.3.0 | 2 / 12 | |
| 2.2.0 | 2 / 12 | |
| 2.1.1 | 2 / 12 | |
| 2.1.0 | 2 / 12 | |
| 2.0.1 | 2 / 12 | |
| 2.0.0 | 2 / 12 | |
| 1.4.3 | 2 / 10 | |
| 1.4.2 | 2 / 10 | |
| 1.4.1 | 2 / 10 | |
| 1.4.0 | 2 / 10 | |
| 1.3.0 | 2 / 10 | |
| 1.2.0 | 2 / 9 | |
| 1.1.0 | 2 / 9 | |
| 1.0.2 | 2 / 9 | |
| 1.0.1 | 2 / 9 | |
| 1.0.0 | 2 / 9 | |
| 0.2.3 | 2 / 9 | |
| 0.2.2 | 2 / 9 | |
| 0.2.1 | 2 / 9 | |
| 0.2.0 | 2 / 9 | |
| 0.1.5 | 2 / 9 | |
| 0.1.4 | 2 / 9 | |
| 0.1.3 | 2 / 9 | |
| 0.1.2 | 2 / 9 | |
| 0.1.1 | 2 / 9 | |
| 0.1.0 | 2 / 9 |
v3.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.4.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-23. 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.
v3.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-05-23. This could indicate a legitimate maintainer transition or an account compromise.
v3.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
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.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
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.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage 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.