@tscircuit/runframe@0.0.3033
⚠ Under review[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 15d ago · by lpm-firewall-aiInspected first-party source shows product analytics and a caller-token registry search, with no confirmed attack behavior. The imported @tscircuit/core and @tscircuit/eval runtime sources remain unresolved, so a clean verdict is not supported.
Decision evidence
public snapshot- The manifest declares @tscircuit/core and @tscircuit/eval as runtime dependencies.
- The runner imports the eval worker and core directly.
- The package exports the preview and runner entrypoints.
- The bundle initializes analytics at its configured tscircuit endpoint and records limited RunFrame activity properties.
- The package search helper sends a supplied session token to the tscircuit registry endpoint.
- The available source does not resolve the behavior of the imported runtime dependencies.
- The inspected credential transfer is tied to a caller-supplied session token and a package-aligned registry search request.
- The inspected analytics activity properties concern the RunFrame component, embedding state, and active tab.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-PJP6TXUJ.jsView on unpkgPackage source references dynamic require/import behavior.
dist/chunk-PJP6TXUJ.jsView on unpkg · L3725Findings
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3033.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3033 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.