require-at — Greenflagged

Call require pretending your are at another directory

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

jchip

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 require-at — it resolves modules relative to a caller-supplied directory. This is intentional design, not a vulnerability.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package is 9+ years old and predates Sigstore provenance on npm; absence is expected for packages of this vintage.	ai	2026/04/24
source-diff	net-exec-file:create-require.js	AI (source-diff): False positive: create-require.js is a Module.createRequire polyfill with no network calls. eval('require') avoids bundler interference.	ai	2026/04/23
semgrep	semgrep:eval-usage	AI (semgrep): eval('require') is a standard pattern to avoid bundler resolution of dynamic requires; only receives literal string 'require'.	ai	2026/04/23

Versions (showing 6 of 6)

Version	Deps	Published
1.0.6	0 / 3	2020-11-28
1.0.5	0 / 3	2020-11-28
1.0.4	0 / 3	2019-01-13
1.0.2	0 / 3	2018-11-16
1.0.1	0 / 3	2018-07-21
1.0.0	0 / 3	2017-02-17

v1.0.6

2 findings

HIGH New file with network + code execution: create-require.js source-diff

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