@tscircuit/runframe@0.0.3011
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 18d ago · by lpm-firewall-aiSource inspection shows no install lifecycle hook or confirmed attack behavior. The flagged network activity is limited to tscircuit-hosted telemetry with narrow activity properties and authenticated package search at the tscircuit registry.
Decision evidence
public snapshot- package.json points to the preview and runner browser entrypoints; its scripts are build and development commands.
- The runtime sends telemetry to tscircuit’s PostHog host and identifies visitors by embed domain or a locally stored anonymous ID.
- The RunFrame telemetry caller supplies only the component, source, embed status, and active tab; the inspected payload contains no circuit files, tokens, or account records.
- Package search sends an optional caller-provided session token to the tscircuit registry search endpoint.
- Browser telemetry initializes by default unless the telemetry-disable flag is set; it can include the embedding domain and anonymous identifier.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-ODMVKCOG.jsView on unpkgPackage source references dynamic require/import behavior.
dist/chunk-ODMVKCOG.jsView on unpkg · L3647Findings
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3011.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3011 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.