requirefresh
Require a file without adding it into the require cache
Supply chain provenance
Status for the latest visible version.
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
Keywords
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 with a variable is the core purpose of requirefresh — it intentionally bypasses the require cache by calling require(resolvedPath). This is a stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package from a trusted publisher with 1348 approved packages; lack of Sigstore provenance is not a material risk signal here. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 5.13.0 | 0 / 16 | |
| 5.12.0 | 0 / 16 | |
| 5.11.0 | 0 / 17 | |
| 5.10.0 | 0 / 18 | |
| 5.9.0 | 0 / 17 | |
| 5.8.0 | 0 / 17 | |
| 5.7.0 | 0 / 17 | |
| 5.6.0 | 0 / 17 | |
| 5.5.0 | 0 / 17 | |
| 5.4.0 | 0 / 17 | |
| 5.1.0 | 0 / 17 | |
| 5.0.0 | 0 / 17 | |
| 4.13.0 | 0 / 13 | |
| 4.12.0 | 0 / 13 | |
| 4.11.0 | 0 / 13 | |
| 4.10.0 | 0 / 13 | |
| 4.9.0 | 0 / 13 | |
| 4.8.0 | 0 / 13 | |
| 4.7.0 | 1 / 13 | |
| 4.6.0 | 0 / 14 | |
| 4.5.0 | 0 / 14 | |
| 4.4.0 | 0 / 14 | |
| 4.3.0 | 0 / 14 | |
| 4.2.0 | 0 / 14 | |
| 4.1.0 | 0 / 14 | |
| 4.0.0 | 0 / 14 | |
| 3.3.0 | 0 / 13 | |
| 3.2.0 | 0 / 13 | |
| 3.1.0 | 0 / 13 | |
| 3.0.0 | 0 / 13 | |
| 2.3.0 | 1 / 17 | |
| 2.2.0 | 1 / 17 | |
| 2.1.0 | 1 / 7 | |
| 2.0.0 | 0 / 5 | |
| 1.1.2 | 0 / 4 | |
| 1.1.1 | 0 / 4 | |
| 1.0.1 | 0 / 4 | |
| 1.0.0 | 0 / 4 |
v5.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.