@tscircuit/runframe@0.0.3075
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe critical scanner hint resolves to an intentional registry sign-in flow, and the captured telemetry fields are limited to UI activity and an anonymous identifier or embed domain. The inspected manifest has no install hook, and no concrete malicious behavior was identified.
Decision evidence
public snapshot- The manifest exports browser preview and runner modules and has no install lifecycle hook.
- Login is initiated by the sign-in handler; its token exchange uses the configured TSCircuit registry API and then updates the registry session.
- Telemetry is browser-only, can be disabled, and skips localhost by default; captured fields are UI activity and an anonymous ID or embed domain.
- The reviewed dependency entrypoints and manifests correspond to the package’s circuit, worker-evaluation, and debugging dependencies.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-KMOEPKMO.jsView on unpkgPackage source references dynamic require/import behavior.
dist/chunk-KMOEPKMO.jsView on unpkg · L3725Findings
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3075.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3075 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.