rcfinder
Find a config file (like .jshintrc) by walking up from a specific 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
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 is the core design of rcfinder — it loads config files by path as part of its rc-file-finding functionality. Not a security risk in this context. | ai | |
| phantom-deps | phantom-dep:expect.js | AI (phantom-deps): expect.js is incorrectly listed in both dependencies and devDependencies; it's a test library packaging mistake, not a phantom dependency security issue. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): spalger is the same person as spenceralger; account rename, not a new maintainer. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): spenceralger → spalger is the same person (Spencer Alger) with a shortened npm handle; not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Small stable utility; dormancy followed by lodash modularization update is expected. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Old account name spenceralger replaced by spalger (same person). | ai | |
| provenance | publisher-changed | AI (provenance): Same author renamed npm account from spenceralger to spalger; legitimate transition. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.1.9 | 1 / 2 | |
| 0.1.8 | 1 / 2 | |
| 0.1.7 | 1 / 2 | |
| 0.1.6 | 1 / 2 | |
| 0.1.5 | 1 / 2 | |
| 0.1.4 | 1 / 2 | |
| 0.1.3 | 0 / 2 | |
| 0.1.2 | 0 / 2 | |
| 0.1.1 | 0 / 2 | |
| 0.1.0 | 1 / 2 |
v0.1.9
3 findingsAll previous maintainers (spenceralger) were replaced by new maintainers (spalger). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2016-05-09. 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.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.