webpack-common-shake MIT 22 versions

webpack-common-shake

npm Repository Homepage

CommonJS Tree Shake Plugin for Webpack

22

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

indutnyjkrems

Keywords

webpackcommonjstreeshake

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 indutny to jkrems occurred in 2018; jkrems is a well-established npm account with 423 approved packages. Legitimate historical transition, not a fresh compromise signal.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): jkrems was added as maintainer in 2018 and has a strong track record. This is a stable, historical maintainer addition, not an active takeover concern.	ai	2026/04/24

Versions (showing 22 of 22)

Version	Deps	Published
2.1.0	4 / 3	2018-09-28
2.0.2	4 / 3	2018-09-24
2.0.1	4 / 3	2018-08-09
2.0.0	4 / 3	2018-08-09
1.5.3	4 / 3	2017-07-09
1.5.2	4 / 3	2017-07-09
1.5.1	4 / 3	2017-07-09
1.5.0	4 / 3	2017-07-08
1.4.0	4 / 3	2017-07-08
1.3.0	4 / 3	2017-07-08
1.2.5	4 / 3	2017-07-08
1.2.4	4 / 3	2017-07-07
1.2.3	4 / 2	2017-07-07
1.2.2	4 / 2	2017-07-06
1.2.1	4 / 2	2017-07-04
1.2.0	4 / 2	2017-07-03
1.1.3	4 / 2	2017-07-03
1.1.2	4 / 2	2017-07-03
1.1.1	4 / 2	2017-07-02
1.1.0	4 / 2	2017-07-02
1.0.1	4 / 2	2017-07-01
1.0.0	4 / 2	2017-07-01

v2.1.0

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

v2.0.0

2 findings

HIGH Publisher changed: indutny → jkrems (on 2018-08-09) provenance

This version was published by a different npm account than previous versions on 2018-08-09. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.5.3

1 finding

LOW No provenance attestation provenance

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

v1.5.2

1 finding

LOW No provenance attestation provenance

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

v1.5.1

1 finding

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.0

1 finding

LOW No provenance attestation provenance

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

v1.3.0

1 finding

LOW No provenance attestation provenance

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

v1.2.5

1 finding

LOW No provenance attestation provenance

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

v1.2.4

1 finding

LOW No provenance attestation provenance

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

v1.2.3

1 finding

LOW No provenance attestation provenance

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

v1.2.2

1 finding

LOW No provenance attestation provenance

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

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.1

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. Only ~12% of npm packages have provenance, so this is common but not ideal.