c12
Smart Config Loader
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): exsolve is a unjs ecosystem package by the same author (pi0), replacing mlly as a module resolver — a legitimate internal refactor, not a supply-chain injection. | ai | |
| dependencies | unvetted-dep:jiti | AI (dependencies): jiti is a well-known unjs ecosystem package by the same author (pi0/Anthony Fu) with millions of weekly downloads; stable false positive for c12. | ai | |
| dependencies | unvetted-dep:pkg-types | AI (dependencies): pkg-types is a well-known unjs ecosystem package with millions of weekly downloads; stable false positive for c12. | ai | |
| bogus-package | bogus-package | AI (bogus-package): pi0 is Anthony Fu, a prolific legitimate OSS developer behind the unjs ecosystem. Spam flag is a false positive; no keywords is trivial for this well-established package. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 3.3.1 | 12 / 12 | |
| 3.2.0 | 12 / 12 | |
| 3.0.4 | 12 / 12 | |
| 3.0.3 | 12 / 12 | |
| 3.0.2 | 12 / 12 | |
| 3.0.1 | 12 / 12 | |
| 3.0.0 | 12 / 12 | |
| 2.0.3 | 12 / 12 | |
| 2.0.2 | 12 / 12 | |
| 2.0.1 | 12 / 12 | |
| 2.0.0 | 12 / 12 | |
| 1.11.2 | 12 / 12 | |
| 1.11.1 | 12 / 12 | |
| 1.11.0 | 12 / 12 | |
| 1.10.0 | 12 / 11 | |
| 1.9.0 | 12 / 11 | |
| 1.8.0 | 13 / 11 | |
| 1.7.0 | 13 / 10 | |
| 1.6.1 | 11 / 10 | |
| 1.6.0 | 11 / 10 | |
| 1.5.1 | 11 / 9 | |
| 1.5.0 | 11 / 9 | |
| 1.4.2 | 11 / 9 | |
| 1.4.1 | 11 / 9 | |
| 1.4.0 | 11 / 9 | |
| 1.3.0 | 8 / 9 | |
| 1.2.0 | 8 / 8 | |
| 1.1.2 | 8 / 8 | |
| 1.1.1 | 8 / 8 | |
| 1.1.0 | 8 / 7 | |
| 1.0.1 | 8 / 7 | |
| 1.0.0 | 8 / 7 | |
| 0.2.13 | 8 / 7 | |
| 0.2.12 | 8 / 7 | |
| 0.2.11 | 8 / 7 | |
| 0.2.10 | 7 / 7 | |
| 0.2.9 | 7 / 7 | |
| 0.2.8 | 7 / 7 | |
| 0.2.7 | 7 / 7 | |
| 0.2.6 | 7 / 7 | |
| 0.2.5 | 7 / 7 | |
| 0.2.4 | 7 / 7 | |
| 0.2.3 | 7 / 7 | |
| 0.2.2 | 7 / 7 | |
| 0.2.1 | 7 / 7 | |
| 0.2.0 | 7 / 7 | |
| 0.1.4 | 7 / 7 | |
| 0.1.3 | 7 / 7 | |
| 0.1.2 | 7 / 7 | |
| 0.1.1 | 7 / 7 | |
| 0.1.0 | 6 / 7 |
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
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.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
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.
v1.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.