@tscircuit/runframe@0.0.3023
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 17d ago · by lpm-firewall-aiSource inspection found first-party RunFrame analytics and an authenticated request to the tscircuit registry, with no package install hook or evidence of unrelated credential transfer. The scanner's exfiltration hint is not supported by the inspected source paths.
Decision evidence
public snapshot- The package entry point is dist/preview.js, and its manifest declares no install lifecycle hook.
- RunFrame telemetry initializes in the browser, supports a telemetry-disable flag, and tracks the first-party tscircuit PostHog host.
- The RunFrame caller sends activity metadata; the telemetry payload includes the embedding domain and anonymous ID.
- The inspected session token is sent as a Bearer token to the tscircuit registry package-search endpoint.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-GXRJTVAG.jsView on unpkgPackage source references dynamic require/import behavior.
dist/chunk-GXRJTVAG.jsView on unpkg · L3647Findings
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3023.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3023 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.