enhanced-resolve
Offers a async require.resolve function. It's highly configurable.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from sokra to thelarkinn is a known legitimate transition within the webpack core team. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): thelarkinn and evilebottnawi are established webpack core team members; legitimate maintainer addition. | ai |
Versions (showing 100 of 130)
| Version | Deps | Published |
|---|---|---|
| 5.22.1 | 2 / 18 | |
| 5.22.0 | 2 / 18 | |
| 5.21.6 | 2 / 18 | |
| 5.21.5 | 2 / 18 | |
| 5.21.4 | 2 / 18 | |
| 5.21.3 | 2 / 18 | |
| 5.21.2 | 2 / 18 | |
| 5.21.1 | 2 / 18 | |
| 5.21.0 | 2 / 18 | |
| 5.20.1 | 2 / 16 | |
| 5.20.0 | 2 / 14 | |
| 5.19.0 | 2 / 14 | |
| 5.18.4 | 2 / 25 | |
| 5.18.3 | 2 / 25 | |
| 5.18.2 | 2 / 25 | |
| 5.18.1 | 2 / 16 | |
| 5.18.0 | 2 / 16 | |
| 5.17.1 | 2 / 16 | |
| 5.17.0 | 2 / 16 | |
| 5.16.1 | 2 / 16 | |
| 5.16.0 | 2 / 16 | |
| 5.15.1 | 2 / 16 | |
| 5.15.0 | 2 / 16 | |
| 5.14.1 | 2 / 16 | |
| 5.14.0 | 2 / 17 | |
| 5.13.0 | 2 / 17 | |
| 5.12.0 | 2 / 17 | |
| 5.11.0 | 2 / 17 | |
| 5.10.0 | 2 / 17 | |
| 5.9.3 | 2 / 17 | |
| 5.9.2 | 2 / 17 | |
| 5.9.1 | 2 / 17 | |
| 5.9.0 | 2 / 17 | |
| 5.8.3 | 2 / 16 | |
| 5.8.2 | 2 / 16 | |
| 5.8.1 | 2 / 16 | |
| 5.8.0 | 2 / 16 | |
| 5.7.0 | 2 / 16 | |
| 5.6.0 | 2 / 16 | |
| 5.5.0 | 2 / 16 | |
| 5.4.1 | 2 / 16 | |
| 5.4.0 | 2 / 16 | |
| 5.3.2 | 2 / 16 | |
| 5.3.1 | 2 / 16 | |
| 5.3.0 | 2 / 16 | |
| 5.2.0 | 2 / 16 | |
| 5.1.0 | 2 / 16 | |
| 5.0.0 | 2 / 16 | |
| 4.5.0 | 3 / 12 | |
| 4.4.0 | 3 / 12 | |
| 4.3.0 | 3 / 12 | |
| 4.2.0 | 3 / 12 | |
| 4.1.1 | 3 / 12 | |
| 4.1.0 | 3 / 10 | |
| 4.0.0 | 3 / 10 | |
| 3.4.1 | 4 / 10 | |
| 3.4.0 | 4 / 10 | |
| 3.3.0 | 4 / 10 | |
| 3.2.0 | 4 / 10 | |
| 3.1.0 | 4 / 10 | |
| 3.0.3 | 4 / 9 | |
| 3.0.2 | 4 / 9 | |
| 3.0.1 | 4 / 9 | |
| 3.0.0 | 4 / 9 | |
| 2.3.0 | 4 / 9 | |
| 2.2.2 | 4 / 9 | |
| 2.2.1 | 4 / 9 | |
| 2.2.0 | 4 / 9 | |
| 2.1.0 | 4 / 9 | |
| 2.0.2 | 4 / 9 | |
| 2.0.1 | 4 / 7 | |
| 2.0.0 | 4 / 7 | |
| 0.9.1 | 3 / 3 | |
| 0.9.0 | 3 / 3 | |
| 0.8.6 | 3 / 3 | |
| 0.8.5 | 3 / 3 | |
| 0.8.4 | 3 / 3 | |
| 0.8.3 | 3 / 3 | |
| 0.8.2 | 3 / 3 | |
| 0.8.1 | 3 / 3 | |
| 0.8.0 | 3 / 3 | |
| 0.7.6 | 3 / 2 | |
| 0.7.5 | 2 / 2 | |
| 0.7.4 | 2 / 2 | |
| 0.7.3 | 1 / 2 | |
| 0.7.2 | 1 / 2 | |
| 0.7.1 | 1 / 2 | |
| 0.7.0 | 1 / 2 | |
| 0.6.1 | 1 / 2 | |
| 0.6.0 | 1 / 2 | |
| 0.5.15 | 1 / 2 | |
| 0.5.14 | 1 / 2 | |
| 0.5.13 | 1 / 2 | |
| 0.5.12 | 1 / 2 | |
| 0.5.11 | 1 / 2 | |
| 0.5.10 | 1 / 2 | |
| 0.5.9 | 1 / 2 | |
| 0.5.8 | 1 / 2 | |
| 0.5.7 | 1 / 2 | |
| 0.5.6 | 1 / 2 |
v5.22.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.22.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.21.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.21.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.21.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.21.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.21.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.21.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.21.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.1
2 findingsThis version was published by a different npm account than previous versions on 2024-02-27. 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.
v5.15.0
2 findingsThis version was published by a different npm account than previous versions on 2023-06-13. 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.
v5.14.1
2 findingsThis version was published by a different npm account than previous versions on 2023-05-24. 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.
v5.14.0
2 findingsThis version was published by a different npm account than previous versions on 2023-05-09. 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.
v5.13.0
2 findingsThis version was published by a different npm account than previous versions on 2023-04-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.
v5.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
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.6.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.1
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.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
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.1.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.