@tscircuit/runframe@0.0.3006
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 19d ago · by lpm-firewall-aiSource inspection found first-party RunFrame analytics with a telemetry disable setting and a caller-invoked EasyEDA proxy that defaults to the same-origin API. The scanner’s credential-transfer signal reflects proxy header forwarding, not a verified transfer of saved service credentials to an unrelated recipient.
Decision evidence
public snapshot- The package exports its browser preview and runner, with no install lifecycle hook declared in the manifest.
- The flagged telemetry identifies an embed domain or anonymous ID and sends RunFrame activity through the first-party PostHog host; telemetry can be disabled through a browser setting.
- The runner reports its component, embedding state, and active tab to the telemetry hook.
- The EasyEDA proxy forwards request headers, including a caller-supplied cookie, to the configured file-server proxy; the API base defaults to the same-origin `/api`, and the helper is used for EasyEDA component fetching.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-6NLV4VEF.jsView on unpkgPackage source references dynamic require/import behavior.
dist/chunk-6NLV4VEF.jsView on unpkg · L3647Findings
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3006.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3006 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.