@tscircuit/props
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 100 of 304)
| Version | Deps | Published |
|---|---|---|
| 0.0.545 | 0 / 16 | |
| 0.0.544 | 0 / 16 | |
| 0.0.543 | 0 / 16 | |
| 0.0.542 | 0 / 16 | |
| 0.0.541 | 0 / 16 | |
| 0.0.540 | 0 / 16 | |
| 0.0.539 | 0 / 16 | |
| 0.0.538 | 0 / 16 | |
| 0.0.537 | 0 / 16 | |
| 0.0.536 | 0 / 16 | |
| 0.0.535 | 0 / 16 | |
| 0.0.534 | 0 / 16 | |
| 0.0.533 | 0 / 16 | |
| 0.0.532 | 0 / 16 | |
| 0.0.531 | 0 / 16 | |
| 0.0.530 | 0 / 16 | |
| 0.0.529 | 0 / 16 | |
| 0.0.528 | 0 / 16 | |
| 0.0.527 | 0 / 16 | |
| 0.0.526 | 0 / 16 | |
| 0.0.525 | 0 / 16 | |
| 0.0.524 | 0 / 16 | |
| 0.0.523 | 0 / 16 | |
| 0.0.522 | 0 / 16 | |
| 0.0.521 | 0 / 16 | |
| 0.0.520 | 0 / 16 | |
| 0.0.519 | 0 / 16 | |
| 0.0.518 | 0 / 16 | |
| 0.0.517 | 0 / 16 | |
| 0.0.516 | 0 / 16 | |
| 0.0.515 | 0 / 16 | |
| 0.0.514 | 0 / 16 | |
| 0.0.513 | 0 / 16 | |
| 0.0.512 | 0 / 16 | |
| 0.0.511 | 0 / 16 | |
| 0.0.510 | 0 / 16 | |
| 0.0.509 | 0 / 16 | |
| 0.0.508 | 0 / 16 | |
| 0.0.507 | 0 / 16 | |
| 0.0.506 | 0 / 16 | |
| 0.0.505 | 0 / 16 | |
| 0.0.504 | 0 / 16 | |
| 0.0.503 | 0 / 16 | |
| 0.0.502 | 0 / 16 | |
| 0.0.501 | 0 / 16 | |
| 0.0.500 | 0 / 16 | |
| 0.0.430 | 0 / 16 | |
| 0.0.429 | 0 / 16 | |
| 0.0.428 | 0 / 16 | |
| 0.0.427 | 0 / 16 | |
| 0.0.426 | 0 / 16 | |
| 0.0.425 | 0 / 16 | |
| 0.0.424 | 0 / 16 | |
| 0.0.423 | 0 / 16 | |
| 0.0.422 | 0 / 16 | |
| 0.0.421 | 0 / 16 | |
| 0.0.420 | 0 / 16 | |
| 0.0.419 | 0 / 16 | |
| 0.0.418 | 0 / 16 | |
| 0.0.417 | 0 / 16 | |
| 0.0.416 | 0 / 16 | |
| 0.0.415 | 0 / 16 | |
| 0.0.414 | 0 / 16 | |
| 0.0.413 | 0 / 16 | |
| 0.0.412 | 0 / 16 | |
| 0.0.411 | 0 / 16 | |
| 0.0.410 | 0 / 16 | |
| 0.0.409 | 0 / 16 | |
| 0.0.408 | 0 / 16 | |
| 0.0.407 | 0 / 16 | |
| 0.0.406 | 0 / 16 | |
| 0.0.405 | 0 / 16 | |
| 0.0.404 | 0 / 16 | |
| 0.0.403 | 0 / 16 | |
| 0.0.402 | 0 / 16 | |
| 0.0.401 | 0 / 16 | |
| 0.0.400 | 0 / 16 | |
| 0.0.399 | 0 / 16 | |
| 0.0.398 | 0 / 16 | |
| 0.0.397 | 0 / 16 | |
| 0.0.396 | 0 / 16 | |
| 0.0.395 | 0 / 16 | |
| 0.0.394 | 0 / 16 | |
| 0.0.393 | 0 / 16 | |
| 0.0.392 | 0 / 16 | |
| 0.0.391 | 0 / 16 | |
| 0.0.390 | 0 / 16 | |
| 0.0.389 | 0 / 16 | |
| 0.0.388 | 0 / 16 | |
| 0.0.387 | 0 / 16 | |
| 0.0.386 | 0 / 16 | |
| 0.0.385 | 0 / 16 | |
| 0.0.384 | 0 / 16 | |
| 0.0.383 | 0 / 16 | |
| 0.0.382 | 0 / 16 | |
| 0.0.381 | 0 / 16 | |
| 0.0.380 | 0 / 16 | |
| 0.0.379 | 0 / 16 | |
| 0.0.378 | 0 / 16 | |
| 0.0.377 | 0 / 16 |
v0.0.545
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.544
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.543
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.542
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.541
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.540
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.539
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.538
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.537
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.536
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.535
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.534
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.533
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.532
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.531
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.530
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.529
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.528
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.527
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.526
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.525
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.524
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.523
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.522
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.521
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.520
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.519
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.518
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.517
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.516
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.515
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.514
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.513
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.512
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.511
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.510
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.509
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.508
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.507
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.506
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.505
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.504
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.503
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.502
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.501
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.500
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.425
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.407
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.387
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v0.0.382
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.381
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.380
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.379
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.378
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.377
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.