tscircuit@0.0.2998
⚠ 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 inspected files show no lifecycle attack or concrete malicious behavior. Because the CLI, core, and eval dependencies are selected runtime dependencies whose source was unresolved, the review cannot establish a clean verdict.
Decision evidence
public snapshot- The package has no install lifecycle hook in its manifest, but its CLI entrypoint imports @tscircuit/cli when run.
- The main export loads @tscircuit/core and @tscircuit/eval, whose source was unavailable in the inspected snapshot.
- The CLI dependency source was also unavailable, so its behavior could not be resolved.
- The inspected @tscircuit/props bundle contains component property schemas and no searched matches for environment access, network requests, child processes, or eval.
- The inspected React entrypoint selects its production or development 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 package has no install lifecycle hook in its manifest, but its CLI entrypoint imports @tscircuit/cli when run.
package.jsonView on unpkg · L17Findings
Affected versions and remediation
This report applies to tscircuit@0.0.2998.
See all versions of tscircuit for other recorded verdicts.
- Review the evidence and your use of tscircuit@0.0.2998 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.