← Home

rcloader

npm Repository Homepage

For build system plugins that need to fetch relative config files (like .jshintrc).

8
Versions
MIT
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

spalger

Keywords

findrcfilercsearchdefaultsconfig

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-takeover AI (maintainer-change): spenceralger → spalger is the same person (Spencer Alger) using a shortened npm handle; change occurred in 2016 with no code changes. ai
provenance publisher-changed AI (provenance): Publisher change is a username migration by the same author (Spencer Alger); spalger is a long-trusted account. ai
maintainer-change maintainer-added AI (maintainer-change): spalger is the same person as spenceralger; legitimate username migration. ai
maintainer-change maintainer-removed AI (maintainer-change): Old username spenceralger removed as part of same-person username migration to spalger. ai

Versions (showing 8 of 8)

Version Deps Published
0.2.2 4 / 2
0.2.1 4 / 2
0.2.0 2 / 2
0.1.4 2 / 2
0.1.2 2 / 2
0.1.1 2 / 2
0.1.0 2 / 2
0.0.1 2 / 2

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

3 findings
HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (spenceralger) were replaced by new maintainers (spalger). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: spenceralger → spalger (on 2016-01-10) provenance

This version was published by a different npm account than previous versions on 2016-01-10. This could indicate a legitimate maintainer transition or an account compromise.

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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.

v0.0.1

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.