requireg No license 12 versions

requireg

npm Repository Homepage

Require and resolve global modules like a boss

12

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

h2non

Keywords

globalnpmmodulesmodulerequireimportresolve

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require is the core purpose of requireg — it resolves and loads globally installed modules by path. This is intentional and expected behavior for this package.	ai	2026/04/23
semgrep	semgrep:child-process-import	AI (semgrep): child_process/spawnSync is used to locate global npm module paths, which is standard and necessary for a global module resolver. Not a supply-chain risk.	ai	2026/04/23

Versions (showing 12 of 12)

Version	Deps	Published
0.2.2	3 / 4	2019-05-24
0.2.1	3 / 4	2018-08-22
0.2.0	3 / 4	2018-08-20
0.1.8	3 / 4	2018-06-02
0.1.7	3 / 4	2017-07-26
0.1.6	2 / 4	2016-09-17
0.1.5	2 / 4	2015-03-29
0.1.4	2 / 3	2015-03-28
0.1.3	1 / 3	2013-12-15
0.1.2	1 / 2	2013-12-12
0.1.1	1 / 2	2013-12-09
0.1.0	1 / 2	2013-12-09

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