@tscircuit/runframe@0.0.3048
⚠ Under review[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe inspected package source does not establish malicious behavior, and its telemetry and registry requests appear tied to RunFrame product functions. The evaluator worker dependency is unresolved in the available source snapshot, so the runtime review cannot support a clean verdict.
Decision evidence
public snapshot- The package exposes browser preview and runner entry points and declares runtime dependencies on the circuit evaluator and core packages.
- The runner imports the evaluator worker, whose resolved source was unavailable for inspection; this leaves a selected runtime dependency unresolved.
- The inspected activity hook sends RunFrame activity properties to telemetry, and the captured identity is an anonymous identifier or embedding domain.
- The manifest contains build and development scripts but no preinstall, install, or postinstall hook.
- The inspected package search sends a caller-provided session token to the tscircuit registry search endpoint.
- The inspected telemetry hook tracks activity metadata; the reviewed excerpt does not show circuit files or credentials being sent.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-HP4Y6X53.jsView on unpkgPackage source references dynamic require/import behavior.
dist/chunk-HP4Y6X53.jsView on unpkg · L3725Findings
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3048.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3048 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.