require-all
An easy way to require all files within a directory.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change felixge→thlorenz occurred in 2012 and has been stable for 12+ years. thlorenz is a well-established publisher with strong approval history. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Maintainer addition of thlorenz is a 12-year-old settled transition, not a recent suspicious change. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is the core purpose of this package — it requires all files in a directory. This is intentional, not malicious. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 0 / 0 | |
| 2.2.0 | 0 / 1 | |
| 2.1.0 | 0 / 1 | |
| 2.0.0 | 0 / 1 | |
| 1.1.0 | 0 / 1 | |
| 1.0.0 | 0 / 1 | |
| 0.0.8 | 0 / 1 | |
| 0.0.6 | 0 / 0 | |
| 0.0.5 | 0 / 0 | |
| 0.0.4 | 0 / 0 | |
| 0.0.3 | 0 / 0 | |
| 0.0.2 | 0 / 0 | |
| 0.0.1 | 0 / 0 |
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
2 findingsThis version was published by a different npm account than previous versions on 2012-11-14. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.