@tscircuit/runframe@0.0.3071
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe scanner’s credential and network hints resolve to an explicit registry sign-in flow and guarded browser telemetry. The manifest has no install lifecycle hook, and the inspected source does not establish malicious behavior.
Decision evidence
public snapshot- The package exports browser preview and runner bundles and has no install lifecycle script.
- Sign-in is user-triggered and sends a temporary login-page token to the registry login-page endpoints.
- The registry client defaults to the TSCircuit registry API; the exchanged session token is stored for registry use.
- Telemetry initialization is browser-only, can be disabled, and skips localhost unless explicitly enabled.
- The inspected dependency entrypoints identify the declared core, eval, and debug packages and show no attack behavior.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-O3IZE2XV.jsView on unpkgPackage source references dynamic require/import behavior.
dist/chunk-O3IZE2XV.jsView on unpkg · L3725Findings
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3071.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3071 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.