@tscircuit/runframe@0.0.3056
⚠ Under review[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe scanner’s credential-exfiltration claim is not supported by the inspected request: the token accompanies a package search to the tscircuit registry. The runner imports unresolved @tscircuit/core and @tscircuit/eval dependencies, so their behavior remains unverified and requires manual review.
Decision evidence
public snapshot- The manifest lists build and development scripts; no install lifecycle hook appears in the inspected scripts.
- Package search sends a caller-provided session token only to the tscircuit registry, with the query in the request body.
- The runtime telemetry code identifies an embed domain or anonymous ID and sends activity to the package-aligned telemetry host.
- The package declares @tscircuit/core and @tscircuit/eval, and the runner imports them; their source could not be resolved in this review, leaving runtime behavior unverified.
- The flagged authorization header is used for a search request to registry-api.tscircuit.com, not an unrelated recipient.
- The inspected telemetry code sends embed-domain or anonymous-ID fields; it does not show credential collection or transfer.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-H6TLCOEL.jsView on unpkgPackage source references dynamic require/import behavior.
dist/chunk-H6TLCOEL.jsView on unpkg · L3725Findings
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3056.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3056 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.