registry / @tscircuit/runframe / 0.0.3091
@tscircuit/runframe@0.0.3091
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe scanner’s exfiltration label is not supported by the inspected source: the cited bearer value is a temporary login-page token used for registry polling and session exchange. Browser analytics use a tscircuit host and anonymous or embed-domain identifiers; no concrete attack surface was found.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The login requests run after a user starts sign-in; telemetry initializes in a browser unless disabled or blocked on localhost.
Impact
The inspected behavior supports registry authentication and product analytics; it does not establish credential theft or an unrelated data recipient.
Mechanism
The login-page token is sent through the registry client to its configured registry API. Analytics submit event properties to the tscircuit PostHog host.
AI rationale
The scanner’s exfiltration label is not supported by the inspected source: the cited bearer value is a temporary login-page token used for registry polling and session exchange. Browser analytics use a tscircuit host and anonymous or embed-domain identifiers; no concrete attack surface was found.
Network endpoints2
registry-api.tscircuit.compostpig.tscircuit.com
Decision evidence
public snapshotAI called this Clean at 89.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json identifies the package entrypoint and contains no install lifecycle hook.
- The login flow creates a registry login page, opens its URL, polls it with the page token, and exchanges it for a CLI session.
- The registry client sends its token to the configurable registry API base, defaulting to registry-api.tscircuit.com.
- Analytics use the tscircuit PostHog host and can be disabled; telemetry identifies an embed domain or anonymous ID and sends event properties.
- The inspected dependency manifests and entrypoints identify ordinary tscircuit libraries and the debug utility.
Evidence against
Behavioral surface
DynamicRequireNetwork
HighEntropyStringsMinifiedUrlStrings
GitDependencyNoLicenseWildcardDependency
Source & flagged code
4 flaggeddist/chunk-Y4OLEBAQ.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-Y4OLEBAQ.js:
const registryApiBaseUrl = getWindowVar("TSCIRCUIT_REGISTRY_API_BASE_URL") || import.meta.env.VITE_TSCIRCUIT_REGISTRY_API_BASE_URL || "https://registry-api.tscircuit.com";
post: (url, options) => getRegistryKy().post(url, options),
var POSTHOG_API_HOST = "https://postpig.tscircuit.com";
return `https://tscircuit.com/editor?${typeParam}#data:application/gzip;base64,${base64Data}`;
const issueUrl = `https://github.com/tscircuit/tscircuit.com/issues/new?title=${encodeURIComponent(
"Initialize a tscircuit project using [tsci init](https://github.com/tscircuit/cli) before adding components.",
"Define reusable modules with cached routes using [<subcircuit />](https://docs.tscircuit.com/elements/subcircuit)",
"Quickly set
Critical
Hardcoded Runtime Data Exfiltration
Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-Y4OLEBAQ.jsView on unpkg3722if (!easyedaBrowserPromise) {
L3723: easyedaBrowserPromise = import(
L3724: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-Y4OLEBAQ.jsView on unpkg · L3722Findings
1 Critical6 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-Y4OLEBAQ.js
MediumDynamic Requiredist/chunk-Y4OLEBAQ.js
MediumNetwork
MediumOversized Source Filedist/standalone.min.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
MediumWildcard Dependency
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
LowNo License
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3091.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3091 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.