require-from-url — Greenflagged

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

may

Keywords

nodejsrequirerequire-from-url

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:toplevel-fetch	AI (semgrep): Fetch at module load is the package's core CLI functionality, not telemetry or exfiltration.	ai	2026/04/29
semgrep	semgrep:child-process-import	AI (semgrep): child_process used to spawn the fetch subprocess as part of documented require-from-url functionality.	ai	2026/04/29

Versions (showing 5 of 5)

Version	Deps	Published
3.1.3	0 / 0	2019-11-03
3.1.2	0 / 0	2017-03-21
3.1.1	0 / 0	2017-03-20
3.1.0	0 / 0	2017-03-19
3.0.0	0 / 0	2017-03-05

v3.1.2

1 finding

LOW No provenance attestation provenance

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

v3.1.1

1 finding

LOW No provenance attestation provenance

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

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

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