circuit-json
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
Versions (showing 51 of 275)
| Version | Deps | Published |
|---|---|---|
| 0.0.433 | 0 / 14 | |
| 0.0.432 | 0 / 14 | |
| 0.0.431 | 0 / 14 | |
| 0.0.430 | 0 / 14 | |
| 0.0.429 | 0 / 14 | |
| 0.0.428 | 0 / 14 | |
| 0.0.427 | 0 / 14 | |
| 0.0.426 | 0 / 14 | |
| 0.0.425 | 0 / 14 | |
| 0.0.424 | 0 / 14 | |
| 0.0.423 | 0 / 14 | |
| 0.0.422 | 0 / 14 | |
| 0.0.421 | 0 / 14 | |
| 0.0.420 | 0 / 14 | |
| 0.0.419 | 0 / 14 | |
| 0.0.418 | 0 / 14 | |
| 0.0.417 | 0 / 14 | |
| 0.0.416 | 0 / 14 | |
| 0.0.415 | 0 / 14 | |
| 0.0.414 | 0 / 14 | |
| 0.0.413 | 0 / 14 | |
| 0.0.412 | 0 / 14 | |
| 0.0.411 | 0 / 14 | |
| 0.0.410 | 0 / 14 | |
| 0.0.409 | 0 / 14 | |
| 0.0.408 | 0 / 14 | |
| 0.0.407 | 0 / 14 | |
| 0.0.406 | 0 / 14 | |
| 0.0.405 | 0 / 14 | |
| 0.0.404 | 0 / 14 | |
| 0.0.403 | 0 / 14 | |
| 0.0.402 | 0 / 14 | |
| 0.0.401 | 0 / 14 | |
| 0.0.400 | 0 / 14 | |
| 0.0.399 | 0 / 14 | |
| 0.0.398 | 0 / 14 | |
| 0.0.397 | 0 / 14 | |
| 0.0.396 | 0 / 14 | |
| 0.0.395 | 0 / 14 | |
| 0.0.394 | 0 / 14 | |
| 0.0.393 | 0 / 14 | |
| 0.0.392 | 0 / 14 | |
| 0.0.391 | 0 / 14 | |
| 0.0.390 | 0 / 14 | |
| 0.0.389 | 0 / 14 | |
| 0.0.388 | 0 / 14 | |
| 0.0.387 | 0 / 14 | |
| 0.0.386 | 0 / 14 | |
| 0.0.385 | 0 / 14 | |
| 0.0.384 | 0 / 14 | |
| 0.0.383 | 0 / 14 |
v0.0.433
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.432
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.431
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.430
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.429
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.428
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.427
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.426
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.425
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.424
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.423
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.422
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.421
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.420
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.419
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.418
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.417
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.416
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.415
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.414
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.413
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.412
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.411
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.410
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.409
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.408
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.407
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.405
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.403
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.399
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.397
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.392
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.389
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.384
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.383
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.