@tscircuit/runframe@0.0.3034
⚠ Under review[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 15d ago · by lpm-firewall-aiThe inspected telemetry and registry requests appear consistent with package features, and no concrete attack was found. The runner imports runtime dependencies whose source was unavailable, so a clean verdict is not supported.
Decision evidence
public snapshot- The manifest points to the preview and runner bundles and declares @tscircuit/core and @tscircuit/eval as runtime dependencies.
- The inspected bundle sends domain or anonymous identifiers and activity properties to the tscircuit telemetry host; telemetry can be disabled with a window flag.
- A supplied session token is sent to the tscircuit registry search endpoint, consistent with the package search feature.
- The runner imports @tscircuit/core and @tscircuit/eval/worker, but their source was unavailable for this review.
- The inspected telemetry payload contains identity and activity metadata, not circuit data or session tokens.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-4RF4PCZ5.jsView on unpkgPackage source references dynamic require/import behavior.
dist/chunk-4RF4PCZ5.jsView on unpkg · L3725Findings
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3034.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3034 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.