@tscircuit/eval
Evaluate code in a full tscircuit runtime environment, including Sucrase transpilation and execution, so you just need to send the code to be executed with automatic handling of imports from `@tsci/*`
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 |
|---|---|---|---|---|
| npm-metadata | url-dep:@tscircuit/jlcpcb-manufacturing-specs | AI (npm-metadata): SHA-pinned devDependency only; not shipped to consumers, and SHA pinning is actually more secure than semver. | ai | |
| source-diff | encoded-string-file:dist/webworker/entrypoint.js | AI (source-diff): Minified bundled SVG/chart code in webworker entrypoint; not an obfuscated payload, stable pattern for this package. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Postinstall runs a local version-copy script and bun install --ignore-scripts; no external fetch or malicious behavior. | ai | |
| source-diff | encoded-string-file:dist/blob-url.js | AI (source-diff): dist/blob-url.js is intentionally built by build:blob-url script to embed a Web Worker as a base64 blob URL. The encoded content is standard ESM bundler boilerplate, not a malicious payload. Stable pattern for this package. | ai |
Versions (showing 100 of 762)
| Version | Deps | Published |
|---|---|---|
| 0.0.401 | 0 / 58 | |
| 0.0.400 | 0 / 58 | |
| 0.0.399 | 0 / 58 | |
| 0.0.398 | 0 / 58 | |
| 0.0.397 | 0 / 58 | |
| 0.0.396 | 0 / 58 | |
| 0.0.395 | 0 / 58 | |
| 0.0.394 | 0 / 58 | |
| 0.0.393 | 0 / 58 | |
| 0.0.392 | 0 / 58 | |
| 0.0.391 | 0 / 58 | |
| 0.0.390 | 0 / 58 | |
| 0.0.389 | 0 / 58 | |
| 0.0.388 | 0 / 58 | |
| 0.0.387 | 0 / 58 | |
| 0.0.386 | 0 / 58 | |
| 0.0.385 | 0 / 58 | |
| 0.0.384 | 0 / 58 | |
| 0.0.383 | 0 / 58 | |
| 0.0.382 | 0 / 58 | |
| 0.0.381 | 0 / 58 | |
| 0.0.380 | 0 / 58 | |
| 0.0.379 | 0 / 58 | |
| 0.0.378 | 0 / 58 | |
| 0.0.377 | 0 / 58 | |
| 0.0.376 | 0 / 58 | |
| 0.0.375 | 0 / 58 | |
| 0.0.374 | 0 / 58 | |
| 0.0.373 | 0 / 58 | |
| 0.0.372 | 0 / 58 | |
| 0.0.371 | 0 / 58 | |
| 0.0.370 | 0 / 58 | |
| 0.0.369 | 0 / 58 | |
| 0.0.368 | 0 / 57 | |
| 0.0.367 | 0 / 57 | |
| 0.0.366 | 0 / 57 | |
| 0.0.365 | 0 / 57 | |
| 0.0.364 | 0 / 57 | |
| 0.0.363 | 0 / 57 | |
| 0.0.362 | 0 / 57 | |
| 0.0.361 | 0 / 57 | |
| 0.0.360 | 0 / 55 | |
| 0.0.359 | 0 / 55 | |
| 0.0.358 | 0 / 55 | |
| 0.0.357 | 0 / 55 | |
| 0.0.356 | 0 / 55 | |
| 0.0.355 | 0 / 55 | |
| 0.0.354 | 0 / 53 | |
| 0.0.353 | 0 / 53 | |
| 0.0.352 | 0 / 53 | |
| 0.0.351 | 0 / 53 | |
| 0.0.350 | 0 / 52 | |
| 0.0.349 | 0 / 52 | |
| 0.0.348 | 0 / 52 | |
| 0.0.347 | 0 / 52 | |
| 0.0.346 | 0 / 52 | |
| 0.0.345 | 0 / 52 | |
| 0.0.344 | 0 / 52 | |
| 0.0.343 | 0 / 53 | |
| 0.0.342 | 0 / 53 | |
| 0.0.341 | 0 / 53 | |
| 0.0.340 | 0 / 53 | |
| 0.0.339 | 0 / 53 | |
| 0.0.338 | 0 / 52 | |
| 0.0.337 | 0 / 52 | |
| 0.0.336 | 0 / 52 | |
| 0.0.335 | 0 / 52 | |
| 0.0.334 | 0 / 52 | |
| 0.0.333 | 0 / 52 | |
| 0.0.332 | 0 / 52 | |
| 0.0.331 | 0 / 52 | |
| 0.0.330 | 0 / 53 | |
| 0.0.329 | 0 / 53 | |
| 0.0.328 | 0 / 53 | |
| 0.0.327 | 0 / 53 | |
| 0.0.326 | 0 / 53 | |
| 0.0.325 | 0 / 53 | |
| 0.0.324 | 0 / 53 | |
| 0.0.323 | 0 / 53 | |
| 0.0.322 | 0 / 53 | |
| 0.0.321 | 0 / 53 | |
| 0.0.320 | 0 / 53 | |
| 0.0.319 | 0 / 53 | |
| 0.0.318 | 0 / 53 | |
| 0.0.317 | 0 / 53 | |
| 0.0.316 | 0 / 53 | |
| 0.0.315 | 0 / 53 | |
| 0.0.314 | 0 / 53 | |
| 0.0.313 | 0 / 53 | |
| 0.0.312 | 0 / 53 | |
| 0.0.311 | 0 / 53 | |
| 0.0.310 | 0 / 53 | |
| 0.0.309 | 0 / 53 | |
| 0.0.308 | 0 / 53 | |
| 0.0.307 | 0 / 53 | |
| 0.0.306 | 0 / 53 | |
| 0.0.305 | 0 / 53 | |
| 0.0.304 | 0 / 53 | |
| 0.0.303 | 0 / 53 | |
| 0.0.302 | 0 / 53 |
v0.0.400
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.390
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.385
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.383
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.380
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.377
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.369
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.365
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.361
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.355
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.351
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.346
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.339
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.337
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.330
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.322
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.319
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.317
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.310
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.