@tscircuit/runframe@0.0.3085
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 7d ago · by lpm-firewall-aiSource inspection ties the flagged runner credential transfers to an explicit service sign-in flow and the returned token is stored for app use. The inspected bundle’s telemetry setup uses an anonymous identifier, and no concrete malicious behavior was established.
Decision evidence
public snapshot- package.json exports the preview and runner entrypoints and declares no lifecycle hooks.
- The runner uses a login-page token to poll the service and exchange the completed login for a CLI session; it stores the returned token for the app.
- The flagged bundle’s registry client uses the configured registry API host, defaulting to registry-api.tscircuit.com, and the app’s registry token.
- The bundle creates a local anonymous ID for telemetry; no credential or rich application record transfer to an unrelated receiver was established.
- The inspected dependency files expose circuit components, a worker, and standard debug routing; no malicious behavior was identified in the reviewed excerpts.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-O6R4VK2K.jsView on unpkgPackage source references dynamic require/import behavior.
dist/chunk-O6R4VK2K.jsView on unpkg · L3722Findings
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3085.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3085 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.