load-cfg
Method that can load project configurations based
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): load-cfg is a config loader that uses @babel/register; @babel/core is a legitimate peer/runtime dep loaded by convention, not a phantom risk. | ai | |
| phantom-deps | phantom-dep:@babel/preset-env | AI (phantom-deps): Same rationale as @babel/core — framework-scoped Babel preset loaded by convention via @babel/register. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established package (2886 days, 7.8k weekly downloads, 100 versions). Sparse README and missing keywords are cosmetic, not security signals. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 2.4.0 | 6 / 0 | |
| 2.1.0 | 6 / 4 | |
| 1.2.0 | 5 / 3 | |
| 1.1.0 | 5 / 3 | |
| 1.0.4 | 5 / 3 | |
| 1.0.2 | 5 / 3 | |
| 1.0.1 | 5 / 3 | |
| 1.0.0 | 5 / 5 | |
| 0.13.3 | 4 / 0 | |
| 0.13.0 | 4 / 0 | |
| 0.12.16 | 4 / 2 | |
| 0.12.15 | 4 / 2 | |
| 0.12.14 | 4 / 2 | |
| 0.12.13 | 4 / 2 | |
| 0.12.10 | 4 / 2 | |
| 0.12.6 | 4 / 2 | |
| 0.12.2 | 4 / 2 | |
| 0.11.1 | 4 / 2 | |
| 0.11.0 | 4 / 2 | |
| 0.10.3 | 3 / 2 | |
| 0.10.0 | 3 / 2 | |
| 0.9.4 | 3 / 2 | |
| 0.9.0 | 3 / 2 | |
| 0.7.0 | 3 / 2 | |
| 0.6.0 | 3 / 2 | |
| 0.5.9 | 3 / 2 | |
| 0.5.6 | 3 / 2 | |
| 0.5.4 | 3 / 2 | |
| 0.5.1 | 3 / 2 | |
| 0.5.0 | 3 / 2 | |
| 0.3.4 | 3 / 2 | |
| 0.3.3 | 3 / 2 | |
| 0.2.8 | 3 / 2 | |
| 0.2.0 | 3 / 2 | |
| 0.1.1 | 3 / 2 | |
| 0.1.0 | 2 / 2 |
v2.4.0
2 findingsThis version was published by a different npm account than previous versions on 2022-02-11. 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.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.