@coast/core-api-types
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal scoped package (@coast org); sparse metadata is consistent with private tooling, not spam. | ai |
Versions (showing 51 of 261)
| Version | Deps | Published |
|---|---|---|
| 1.2.338 | 9 / 7 | |
| 1.2.337 | 9 / 7 | |
| 1.2.336 | 9 / 7 | |
| 1.2.335 | 9 / 7 | |
| 1.2.334 | 9 / 7 | |
| 1.2.333 | 9 / 7 | |
| 1.2.332 | 9 / 7 | |
| 1.2.331 | 9 / 7 | |
| 1.2.330 | 9 / 7 | |
| 1.2.320 | 9 / 7 | |
| 1.2.319 | 9 / 7 | |
| 1.2.318 | 9 / 7 | |
| 1.2.317 | 9 / 7 | |
| 1.2.316 | 9 / 7 | |
| 1.2.315 | 9 / 7 | |
| 1.2.314 | 9 / 7 | |
| 1.2.313 | 9 / 7 | |
| 1.2.312 | 9 / 7 | |
| 1.2.311 | 9 / 7 | |
| 1.2.310 | 9 / 7 | |
| 1.2.309 | 9 / 7 | |
| 1.2.308 | 9 / 7 | |
| 1.2.307 | 9 / 7 | |
| 1.2.306 | 9 / 7 | |
| 1.2.305 | 9 / 7 | |
| 1.2.304 | 9 / 7 | |
| 1.2.303 | 9 / 7 | |
| 1.2.302 | 9 / 7 | |
| 1.2.301 | 9 / 7 | |
| 1.2.300 | 9 / 7 | |
| 1.2.299 | 9 / 7 | |
| 1.2.298 | 9 / 7 | |
| 1.2.297 | 9 / 7 | |
| 1.2.296 | 9 / 7 | |
| 1.2.295 | 9 / 7 | |
| 1.2.294 | 9 / 7 | |
| 1.2.293 | 9 / 7 | |
| 1.2.292 | 9 / 7 | |
| 1.2.291 | 9 / 7 | |
| 1.2.290 | 9 / 7 | |
| 1.2.289 | 9 / 7 | |
| 1.2.288 | 9 / 7 | |
| 1.2.287 | 9 / 7 | |
| 1.2.286 | 9 / 7 | |
| 1.2.285 | 9 / 6 | |
| 1.2.284 | 9 / 6 | |
| 1.2.283 | 9 / 6 | |
| 1.2.282 | 9 / 6 | |
| 1.2.281 | 9 / 6 | |
| 1.2.280 | 9 / 6 | |
| 1.2.279 | 9 / 6 |
v1.2.338
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.337
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.336
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.335
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.334
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.333
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.332
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.331
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.330
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.320
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.319
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.318
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.317
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.316
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.315
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.314
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.313
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.312
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.311
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.310
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.309
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.308
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.307
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.282
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.281
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.280
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.279
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.