tscircuit@0.0.2976
⚠ Under reviewMake electronics using Typescript, React, and AI tools. Just prompt your agent to "use tscircuit" and 10x its PCB capabilities!
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe inspected package source shows no install lifecycle hook or concrete attack behavior. Because its runtime entrypoints load selected dependencies whose source could not be assessed, the package cannot be cleared from this snapshot.
Decision evidence
public snapshot- The manifest points to dist/index.js as the library entry and declares @tscircuit/core and @tscircuit/eval as dependencies.
- The library entry re-exports @tscircuit/core and @tscircuit/eval, so those packages are loaded through the runtime entry.
- The CLI entrypoint imports @tscircuit/cli when invoked.
- The selected core, eval, and CLI dependency source was unresolved or unavailable in the inspected package snapshot, so their runtime behavior could not be assessed.
- The inspected manifest lists no preinstall, install, or postinstall script.
- The inspected @tscircuit/props manifest contains build and maintenance scripts, with no install lifecycle script shown.
- The inspected React entry selects its development or production module based on NODE_ENV.
Source & flagged code
6 flaggedPackage contains source files above the normal full-analysis size ceiling.
dist/webworker.min.jsView on unpkgThe manifest points to dist/index.js as the library entry and declares @tscircuit/core and @tscircuit/eval as dependencies.
package.jsonView on unpkg · L3Findings
Affected versions and remediation
This report applies to tscircuit@0.0.2976.
See all versions of tscircuit for other recorded verdicts.
- Review the evidence and your use of tscircuit@0.0.2976 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.