@tscircuit/runframe@0.0.3042
⚠ Under review[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe flagged bundle behavior inspected is consistent with Runframe file and event APIs and tscircuit-hosted activity analytics; it did not establish credential theft or rich-record exfiltration. The selected @tscircuit/core and @tscircuit/eval runtime sources remain unresolved, so a clean verdict is not supported.
Decision evidence
public snapshot- package.json declares @tscircuit/core and @tscircuit/eval as runtime dependencies.
- dist/runner.js imports the eval worker, making that dependency part of the runner’s runtime path.
- The bundle’s file API uses a configurable base that defaults to the relative /api path.
- The inspected bundle sends Runframe activity fields to tscircuit-hosted analytics, with a telemetry disable flag and localhost guard; no credential or rich application-record transfer was established.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-YEO43MKD.jsView on unpkgPackage source references dynamic require/import behavior.
dist/chunk-YEO43MKD.jsView on unpkg · L3725Findings
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3042.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3042 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.