@cosmology/ast
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped @cosmology/ast is not a typosquat of jest; Levenshtein match is a false positive. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped @cosmology/ast is not a typosquat of got; Levenshtein match is a false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): Scoped @cosmology/ast is not a typosquat of qs; Levenshtein match is a false positive. | ai | |
| typosquat | typosquat.levenshtein:ajv | AI (typosquat): Scoped @cosmology/ast is not a typosquat of ajv; Levenshtein match is a false positive. | ai | |
| phantom-deps | phantom-dep:dotty | AI (phantom-deps): dotty is a declared runtime dependency in package.json; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.2.0 | 6 / 9 | |
| 2.1.0 | 5 / 19 | |
| 2.0.3 | 5 / 19 | |
| 2.0.2 | 5 / 19 | |
| 2.0.1 | 5 / 19 | |
| 2.0.0 | 5 / 19 |
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.