@tscircuit/runframe@0.0.3050
⚠ Under review[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe inspected source shows browser telemetry and a proxy used for component import, but does not establish malicious behavior. The dependency imports and proxy credential flow remain unresolved, so the source does not support a clean verdict or a confirmed attack.
Decision evidence
public snapshot- The manifest declares @tscircuit/core and @tscircuit/eval dependencies, and the runtime imports both.
- The browser runtime forwards a supplied cookie header through a proxy request whose API base can be configured; the credential source and recipient behavior are not resolved from the inspected source.
- Telemetry initializes in the browser and can be disabled through a global setting.
- The manifest has no install lifecycle hook, and the inspected proxy path is used by the EasyEDA component import feature.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-S7QVCXIA.jsView on unpkgPackage source references dynamic require/import behavior.
dist/chunk-S7QVCXIA.jsView on unpkg · L3725Findings
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3050.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3050 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.