vite-plugin-commonjs No license 43 versions

vite-plugin-commonjs

npm Repository Homepage

43

Versions

—

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

youngleicaoxie

Keywords

viteplugincommonjsrequire

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:fast-glob	AI (phantom-deps): Likely used in build/config, false positive typical for bundled plugin code.	ai	2026/07/21
maintainer-change	maintainer-takeover	AI (maintainer-change): Matched known maintainer email; long-lived version, not a fresh takeover.	ai	2026/07/21
maintainer-change	maintainer-added	AI (maintainer-change): Same person as prior maintainer, different account.	ai	2026/07/21
maintainer-change	maintainer-removed	AI (maintainer-change): Alias consolidation, not real removal.	ai	2026/07/21
dependencies	unvetted-dep:cjs-esm	AI (dependencies): Small legitimate helper dep, no execution/exfil behavior observed.	ai	2026/07/21

Versions (showing 43 of 43)

Version	Deps	Published
0.10.4	3 / 7	2024-11-21
0.10.3	3 / 7	2024-09-16
0.10.2	4 / 6	2024-09-15
0.10.1	4 / 6	2023-11-14
0.10.0	4 / 6	2023-10-08
0.9.0	4 / 6	2023-08-26
0.8.2	4 / 6	2023-07-17
0.8.1	4 / 6	2023-07-12
0.8.0	3 / 6	2023-06-24
0.7.1	3 / 6	2023-05-14
0.7.0	3 / 6	2023-04-30
0.6.2	1 / 5	2023-03-12
0.6.1	1 / 5	2022-12-10
0.6.0	1 / 5	2022-11-27
0.5.3	1 / 5	2022-10-16
0.5.2	2 / 3	2022-06-21
0.5.1	2 / 3	2022-06-20
0.5.0	2 / 3	2022-06-16
0.4.7	1 / 3	2022-05-13
0.4.6	1 / 3	2022-05-12
0.4.5	1 / 3	2022-05-11
0.4.4	1 / 3	2022-05-06
0.4.3	1 / 3	2022-05-06
0.4.2	1 / 3	2022-05-06
0.4.1	1 / 3	2022-05-06
0.4.0	1 / 3	2022-05-06
0.3.2	1 / 3	2022-05-05
0.3.1	1 / 3	2022-05-04
0.3.0	0 / 4	2022-05-04
0.2.6	3 / 4	2021-10-19
0.2.5	3 / 4	2021-10-12
0.2.4	3 / 4	2021-10-12
0.2.3	3 / 4	2021-09-22
0.2.2	3 / 4	2021-09-22
0.2.1	3 / 4	2021-09-16
0.2.0	3 / 4	2021-09-08
0.1.5	2 / 4	2021-08-14
0.1.4	2 / 4	2021-08-09
0.1.3	2 / 4	2021-08-09
0.1.2	2 / 4	2021-08-09
0.1.1	2 / 4	2021-08-09
0.1.0	2 / 4	2021-08-08
0.0.1	2 / 4	2021-08-08

v0.10.3

1 finding

LOW No provenance attestation provenance

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

v0.10.2

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.

v0.10.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2023-11-14, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2023-11-14, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.10.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2023-10-08, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2023-10-08, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.9.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2023-08-26, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2023-08-26, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.8.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2023-07-17, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2023-07-17, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.8.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2023-07-12, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2023-07-12, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.8.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2023-06-24, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2023-06-24, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.7.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2023-05-14, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2023-05-14, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.7.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2023-04-30, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2023-04-30, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.6.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2023-03-12, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2023-03-12, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.6.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2022-12-10, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2022-12-10, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.6.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2022-11-27, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2022-11-27, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.5.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2022-10-16, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2022-10-16, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.5.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2022-06-21, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2022-06-21, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.5.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2022-06-20, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2022-06-20, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.5.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2022-06-16, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2022-06-16, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.4.7

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2022-05-13, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2022-05-13, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.4.6

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2022-05-12, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2022-05-12, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.4.5

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2022-05-11, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2022-05-11, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.4.4

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2022-05-06, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2022-05-06, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.4.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2022-05-06, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2022-05-06, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.4.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2022-05-06, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2022-05-06, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.4.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2022-05-06, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2022-05-06, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.4.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2022-05-06, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2022-05-06, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.3.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2022-05-05, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2022-05-05, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.3.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2022-05-04, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2022-05-04, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.3.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: caoxiemeihao → caoxie (on 2022-05-04, known maintainer) provenance

This version was published by a different npm account (caoxie) than the most recent previously approved version (caoxiemeihao) on 2022-05-04, but caoxie is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.2.6

1 finding

LOW No provenance attestation provenance

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

v0.2.5

1 finding

LOW No provenance attestation provenance

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

v0.2.4

1 finding

LOW No provenance attestation provenance

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

v0.2.3

1 finding

LOW No provenance attestation provenance

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

v0.2.2

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

1 finding

LOW No provenance attestation provenance

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

v0.1.4

1 finding

LOW No provenance attestation provenance

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

v0.1.3

1 finding

LOW No provenance attestation provenance

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

v0.1.2

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.

v0.0.1

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.