@tscircuit/runframe@0.0.3070
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 9d ago · by lpm-firewall-aiSource inspection resolved the credential findings as user-started authentication with the tscircuit registry, and the flagged telemetry is tscircuit-hosted and uses anonymous or embedding-domain identifiers. The scanner’s malicious label is not supported by the inspected behavior.
Decision evidence
public snapshot- The manifest exposes browser UI bundles and lists no install lifecycle hook; the runner and its imported dependencies are ordinary runtime components.
- The flagged authorization requests occur inside a sign-in handler and send login-page credentials to the configured tscircuit registry; the resulting session token is stored for tscircuit use.
- The registry client defaults to registry-api.tscircuit.com, and the shared chunk’s PostHog code sends anonymous or embedding-domain telemetry to the tscircuit analytics host.
- The inspected core and eval entry sources support circuit rendering and worker evaluation; the inspected debug source selects its browser or Node implementation.
- The flagged shared chunk contains registry and file-server APIs aligned with the package’s runframe UI; no unrelated credential recipient or concrete attack behavior was identified.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-NTCJO4DR.jsView on unpkgPackage source references dynamic require/import behavior.
dist/chunk-NTCJO4DR.jsView on unpkg · L3725Findings
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3070.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3070 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.