registry / @tscircuit/runframe / 0.0.3005
@tscircuit/runframe@0.0.3005
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 19d ago · by lpm-firewall-aiSource inspection found no install hook or confirmed attack surface. The scanner’s credential finding resolves to a session token sent to the package’s own registry for package search; telemetry uses the package’s own collector and identity scheme.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Telemetry initializes when the browser bundle loads; registry search runs when requested by the UI.
Impact
The inspected behavior does not establish credential theft or another attack.
Mechanism
Telemetry sends RunFrame activity with an embedding-domain or anonymous identity to the tscircuit collector. Registry search sends its optional session token to the tscircuit registry.
AI rationale
Source inspection found no install hook or confirmed attack surface. The scanner’s credential finding resolves to a session token sent to the package’s own registry for package search; telemetry uses the package’s own collector and identity scheme.
Network endpoints2
postpig.tscircuit.comregistry-api.tscircuit.com/packages/search
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json points to browser library exports and contains no install lifecycle hook.
- The flagged telemetry uses the package’s tscircuit collector and derives identity from the embedding domain or an anonymous ID.
- Registry search sends its optional session token to the tscircuit registry for a package search.
Evidence against
Behavioral surface
DynamicRequireNetwork
HighEntropyStringsMinifiedUrlStrings
GitDependencyNoLicenseWildcardDependency
Oversized source lightweight scan
dist/standalone-preview.min.js
Source & flagged code
4 flaggeddist/chunk-YTIFTXYA.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-YTIFTXYA.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-YTIFTXYA.jsView on unpkg3647if (!easyedaBrowserPromise) {
L3648: easyedaBrowserPromise = import(
L3649: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-YTIFTXYA.jsView on unpkg · L3647Findings
1 Critical6 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-YTIFTXYA.js
MediumDynamic Requiredist/chunk-YTIFTXYA.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.3005.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3005 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.