cosmiconfig-typescript-loader
TypeScript loader for cosmiconfig
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): jiti is a legitimate, widely-used TypeScript runtime loader; its addition is consistent with this package's purpose as a TypeScript loader for cosmiconfig. | ai | |
| dependencies | unvetted-dep:jiti | AI (dependencies): jiti is the core runtime dependency for TypeScript loading — its use is fundamental to this package's purpose and expected across all versions. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed from personal account to GitHub Actions CI/CD, confirmed by SLSA provenance attestation. Legitimate automation transition. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Stable, mature package with 8.1M weekly downloads; infrequent publishes are normal for this lifecycle stage. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 6.3.0 | 1 / 18 | |
| 6.2.0 | 1 / 18 | |
| 6.1.0 | 1 / 17 | |
| 6.0.0 | 1 / 17 | |
| 5.1.0 | 1 / 16 | |
| 5.0.0 | 1 / 16 | |
| 4.4.0 | 0 / 15 | |
| 4.3.0 | 0 / 13 | |
| 4.2.0 | 0 / 13 | |
| 4.1.1 | 0 / 14 | |
| 4.1.0 | 0 / 14 | |
| 4.0.0 | 0 / 14 | |
| 3.1.2 | 0 / 14 | |
| 3.1.1 | 0 / 14 | |
| 3.1.0 | 0 / 14 | |
| 3.0.0 | 0 / 12 | |
| 2.0.2 | 2 / 12 | |
| 2.0.1 | 2 / 12 | |
| 2.0.0 | 2 / 12 | |
| 1.0.9 | 2 / 12 | |
| 1.0.8 | 2 / 12 | |
| 1.0.7 | 2 / 12 | |
| 1.0.6 | 2 / 12 | |
| 1.0.5 | 2 / 12 | |
| 1.0.4 | 2 / 12 | |
| 1.0.3 | 2 / 12 | |
| 1.0.2 | 2 / 12 | |
| 1.0.1 | 2 / 12 | |
| 1.0.0 | 2 / 12 | |
| 0.0.9 | 2 / 12 | |
| 0.0.8 | 2 / 12 | |
| 0.0.7 | 2 / 12 | |
| 0.0.6 | 2 / 12 | |
| 0.0.5 | 2 / 12 | |
| 0.0.4 | 2 / 12 | |
| 0.0.3 | 2 / 12 | |
| 0.0.2 | 2 / 12 |
v6.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-09. 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.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.