tscircuit@0.0.3000
⚠ 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 14d ago · by lpm-firewall-aiThe reviewed entrypoints and available dependency excerpts establish no concrete attack, but source for selected runtime dependencies including @tscircuit/core and @tscircuit/cli was unavailable. This unresolved execution path requires manual review rather than a clean or malicious verdict.
Decision evidence
public snapshot- The manifest points to dist/index.js and declares no install lifecycle hook.
- The CLI sets a package-local browser bundle path only when the environment variable is unset, then imports @tscircuit/cli.
- The library entrypoint exports from @tscircuit/core and @tscircuit/eval; source for these dependencies was unavailable for this review.
- The inspected @tscircuit/props bundle begins with type checks and component property definitions; the inspected React entrypoint selects its production or development build.
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 and declares no install lifecycle hook.
package.jsonView on unpkg · L1Findings
Affected versions and remediation
This report applies to tscircuit@0.0.3000.
See all versions of tscircuit for other recorded verdicts.
- Review the evidence and your use of tscircuit@0.0.3000 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.