rc-config-loader
load config file from .{product}rc.{json,yml,js}
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher changed to GitHub Actions reflects automated CI/CD publishing by original maintainer azu; SLSA provenance attestation confirms integrity. This pattern is stable for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 4.1.4 | 4 / 9 | |
| 4.1.3 | 4 / 9 | |
| 4.1.2 | 4 / 9 | |
| 4.1.1 | 4 / 9 | |
| 4.1.0 | 4 / 12 | |
| 4.0.0 | 4 / 12 | |
| 3.0.0 | 4 / 11 | |
| 2.0.5 | 7 / 14 | |
| 2.0.4 | 7 / 14 | |
| 2.0.3 | 7 / 13 | |
| 2.0.2 | 7 / 13 | |
| 2.0.1 | 7 / 13 | |
| 2.0.0 | 7 / 10 | |
| 1.0.2 | 7 / 10 | |
| 1.0.1 | 7 / 10 |
v4.1.4
2 findingsThis version was published by a different npm account than previous versions on 2026-02-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.