@tscircuit/runframe@0.0.3077
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 8d ago · by lpm-firewall-aiSource inspection shows the flagged token transfer follows a visible user sign-in flow and sends the resulting session token to the configured file-server API, whose default is same-origin. The manifest has no install hook, and the other inspected flagged behaviors are conditional feature paths; no concrete attack behavior was found.
Decision evidence
public snapshot- The manifest points to browser preview and runner bundles and lists build and development scripts; it has no install lifecycle hook.
- Sign-in starts from a visible button. The runner creates a registry login page, polls it with its short-lived login-page token, and exchanges it for a session token at the registry API.
- After sign-in, the session token is stored in the window and included in a TOKEN_UPDATED event. Events go to the configured file-server API, which defaults to the same-origin /api path.
- The core dependency defaults autorouting to the tscircuit registry API. The eval worker enables fetch proxying only when its configuration requests it; the debug entry selects browser or Node behavior.
- The JLCPCB import path requires a supplied handler and passes the configured proxy headers and API base to the import function.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-Z5SPOJTX.jsView on unpkgPackage source references dynamic require/import behavior.
dist/chunk-Z5SPOJTX.jsView on unpkg · L3725Findings
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3077.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3077 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.