loader-runner
Runs (webpack) loaders
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval("import(...)") is a standard CJS-to-ESM dynamic import workaround; input is JSON-stringified URL from a resolved loader path, not arbitrary user input. Stable false positive for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): require(loader.path) is the core function of loader-runner — loading webpack loaders by resolved path. This is expected and intentional behavior, not a supply-chain risk. | ai | |
| provenance | no-provenance | AI (provenance): Established webpack core package published by sokra; lack of Sigstore provenance is common and not a risk indicator here. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.3.2 | 0 / 17 | |
| 4.3.1 | 0 / 17 | |
| 4.3.0 | 0 / 6 | |
| 4.2.0 | 0 / 6 | |
| 4.1.0 | 0 / 8 | |
| 4.0.0 | 0 / 8 | |
| 3.1.0 | 0 / 8 | |
| 3.0.0 | 0 / 8 |
v4.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.