@tscircuit/runframe@0.0.3047
⚠ Under review[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe flagged telemetry is limited in the inspected code to viewer activity and identity metadata, which does not establish an attack. The manifest and runner show selected runtime dependencies whose source could not be reviewed, so the package remains unresolved rather than clean.
Decision evidence
public snapshot- The manifest has no install lifecycle hooks, but the runtime imports two selected dependencies whose source was unavailable for this review.
- The flagged telemetry records the embedding domain, anonymous identifier, component, and active tab; the inspected code does not show application records or credentials in that event.
- The browser telemetry uses the package’s PostHog project and a tscircuit host, and can be disabled through a browser setting.
- The package entrypoints expose viewer components; the telemetry hook runs when those components render.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-VAQWX7I2.jsView on unpkgPackage source references dynamic require/import behavior.
dist/chunk-VAQWX7I2.jsView on unpkg · L3725Findings
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3047.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3047 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.