vite-plugin-node-polyfills No license 30 versions

vite-plugin-node-polyfills

npm Repository Homepage

30

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

davidmyersdev

Keywords

nodenode-core-modulesnode-polyfillsnode-stdlibpolyfillsvitevite-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:process-polyfill	AI (dependencies): Aliased official npm:process; core to a Node-polyfill plugin.	ai	2026/07/21
source-diff	obfuscated-file:test/dist/assets/index.4fbd3315.js	AI (source-diff): Minified Vite build output in test fixture dir; not obfuscation, stable for this package.	ai	2026/07/21
source-diff	obfuscated-file:test/dist/assets/index.e0a0e754.js	AI (source-diff): Vite-built test fixture bundle (minified), not obfuscation; benign build output.	ai	2026/07/21

Versions (showing 30 of 30)

Version	Deps	Published
0.28.0	2 / 16	2026-05-18
0.27.0	2 / 16	2026-05-15
0.26.0	2 / 16	2026-03-29
0.25.0	2 / 16	2026-01-15
0.24.0	2 / 16	2025-07-06
0.23.1	2 / 16	2025-07-05
0.23.0	2 / 16	2025-01-19
0.22.0	2 / 16	2024-05-19
0.11.2	4 / 18	2023-08-17
0.11.0	4 / 17	2023-08-06
0.8.2	2 / 9	2023-04-26
0.8.1	2 / 9	2023-04-11
0.8.0	2 / 9	2023-04-11
0.7.0	2 / 9	2023-01-10
0.6.0	2 / 9	2022-12-26
0.5.0	2 / 9	2022-10-29
0.4.0	2 / 8	2022-10-01
0.3.2	2 / 8	2022-10-01
0.3.1	2 / 7	2022-09-30
0.3.0	2 / 7	2022-09-30
0.2.0	3 / 4	2022-09-30
0.1.8	3 / 4	2022-08-26
0.1.7	3 / 4	2022-08-25
0.1.6	3 / 4	2022-08-25
0.1.5	3 / 4	2022-08-25
0.1.4	3 / 4	2022-08-25
0.1.3	3 / 4	2022-08-25
0.1.2	3 / 4	2022-08-25
0.1.1	0 / 7	2022-08-25
0.1.0	2 / 4	2022-08-25

v0.23.0

1 finding

LOW No provenance attestation provenance

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

v0.22.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.11.2

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: voraciousdev.

LOW No provenance attestation provenance

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

v0.11.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: voraciousdev.

LOW No provenance attestation provenance

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

v0.8.2

1 finding

LOW No provenance attestation provenance

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

v0.8.1

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.2

2 findings

HIGH New obfuscated file: test/dist/assets/index.4fbd3315.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.3.1

2 findings

HIGH New obfuscated file: test/dist/assets/index.e0a0e754.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v0.3.0

2 findings

HIGH New obfuscated file: test/dist/assets/index.e0a0e754.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

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

1 finding

LOW No provenance attestation provenance

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

v0.1.7

1 finding

LOW No provenance attestation provenance

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

v0.1.6

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.