@webpack-contrib/config-loader MIT 11 versions

@webpack-contrib/config-loader

npm Repository Homepage

A webpack configuration loader

11

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

bebrawd3viant0neevilebottnawijhnnsjtangeldermichael-ciniawskyshellscapesokrathelarkinn

Keywords

webpack

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require is the core functionality of a config loader — it must load user-specified webpack config files by path. This pattern is intentional and stable across all versions.	ai	2026/04/23
phantom-deps	phantom-dep:loud-rejection	AI (phantom-deps): loud-rejection is a declared runtime dependency; it may be used via side-effect import. False positive for this package.	ai	2026/04/23

Versions (showing 11 of 11)

Version	Deps	Published
1.2.1	9 / 35	2018-07-02
1.2.0	9 / 35	2018-07-02
1.1.3	8 / 35	2018-05-29
1.1.2	7 / 36	2018-05-27
1.1.1	6 / 36	2018-05-09
1.1.0	5 / 36	2018-05-09
1.0.0	5 / 36	2018-05-08
0.2.1	6 / 36	2018-04-28
0.2.0	6 / 36	2018-04-26
0.1.1	6 / 36	2018-04-19
0.1.0	6 / 36	2018-04-10

v1.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.