← Home

rollup-plugin-node-builtins

npm Repository Homepage

use node builtins in browser with rollup

15
Versions
ISC
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

cwmma

Keywords

rollup-plugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff net-exec-file:src/es6/setimmediate.js AI (source-diff): This is the YuzuJS/setImmediate MIT-licensed browser polyfill. new Function() is the spec-compliant string-callback path; no actual network exfiltration present. ai
source-diff net-exec-file:src/es6/vm.js AI (source-diff): This is the substack/vm-browserify MIT-licensed shim. new Function() is inherent to implementing vm.runInNewContext() in browsers; no malicious network activity. ai
semgrep semgrep:new-function-constructor AI (semgrep): new Function() in setimmediate.js is a standard pattern in the setimmediate polyfill for handling string callbacks per spec; not a malicious code execution vector for this package. ai
publish-pattern new-deps-added AI (publish-pattern): browserify-fs is a legitimate Node.js fs shim; adding it is consistent with this package's purpose of polyfilling Node builtins for browser use. ai

Versions (showing 15 of 15)

Version Deps Published
2.1.2 4 / 7
2.1.1 4 / 7
2.1.0 4 / 7
2.0.0 3 / 7
1.2.1 3 / 7
1.2.0 3 / 6
1.1.0 3 / 6
1.0.8 4 / 9
1.0.7 4 / 7
1.0.6 3 / 8
1.0.5 3 / 8
1.0.3 5 / 6
1.0.2 5 / 6
1.0.1 5 / 6
1.0.0 1 / 7

v2.1.2

1 finding
LOW No provenance attestation provenance

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

v2.1.1

1 finding
LOW No provenance attestation provenance

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

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

3 findings
HIGH New file with network + code execution: src/es6/setimmediate.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: src/es6/vm.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v1.2.0

3 findings
HIGH New file with network + code execution: src/es6/setimmediate.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

HIGH New file with network + code execution: src/es6/vm.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

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

1 finding
LOW No provenance attestation provenance

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

v1.0.7

1 finding
LOW No provenance attestation provenance

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

v1.0.6

1 finding
LOW No provenance attestation provenance

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

v1.0.5

1 finding
LOW No provenance attestation provenance

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

v1.0.3

1 finding
LOW No provenance attestation provenance

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

v1.0.2

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.