@tscircuit/runframe@0.0.3084
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe flagged credential flow is part of an explicit registry sign-in and uses the registry API. Automatic analytics sends limited UI activity context to the package vendor; the inspected code does not send credentials or project records.
Decision evidence
public snapshot- The package exports browser UI components through its preview and runner entry points.
- Analytics uses the tscircuit-hosted PostHog endpoint and an anonymous identifier or embedding domain.
- The activity event is limited to source, component, embedded status, and active tab; the runner passes those fields when its UI mounts.
- Registry bearer tokens are used with the configurable registry API, and the shown sign-in flow starts from an explicit handler.
- Analytics initializes automatically by default, though the inspected event contains usage context rather than credentials or project records.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-HBIXBCIB.jsView on unpkgPackage source references dynamic require/import behavior.
dist/chunk-HBIXBCIB.jsView on unpkg · L3725Findings
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3084.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3084 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.