registry / @tscircuit/runframe / 0.0.3046
@tscircuit/runframe@0.0.3046
⚠ 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 bundle’s telemetry targets the package’s project host, and inspected code does not show credentials being forwarded there. The manifest’s @tscircuit/core and @tscircuit/eval dependencies are imported by the runner but their source snapshots are unresolved, so a clean verdict is not supported.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Telemetry initializes when the browser bundle loads and reports activity when the preview component is used.
Impact
No concrete attack impact was established, but behavior in the unresolved dependencies could not be assessed.
Mechanism
PostHog sends preview identity and activity data to the configured tscircuit host; the runner also imports unresolved runtime dependencies.
AI rationale
The flagged bundle’s telemetry targets the package’s project host, and inspected code does not show credentials being forwarded there. The manifest’s @tscircuit/core and @tscircuit/eval dependencies are imported by the runner but their source snapshots are unresolved, so a clean verdict is not supported.
Evidence
package.jsondist/runner.jsdist/chunk-O7UDYGZW.js
Network endpoints1
postpig.tscircuit.com
Decision evidence
public snapshotAI called this Manual Review at 83.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest declares @tscircuit/core and @tscircuit/eval as runtime dependencies, and the runner imports both.
- The available source snapshots for debug and @tscircuit/solver-utils were inspected; the declared @tscircuit/core and @tscircuit/eval sources remain unresolved.
- The flagged bundle configures project telemetry to the package’s tscircuit host and can report preview error details.
Evidence against
- Inspected source shows the flagged host is used for PostHog telemetry, and I found no source showing registry credentials being sent to it.
Behavioral surface
DynamicRequireNetwork
HighEntropyStringsMinifiedUrlStrings
GitDependencyNoLicenseWildcardDependency
Source & flagged code
4 flaggeddist/chunk-O7UDYGZW.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-O7UDYGZW.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-O7UDYGZW.jsView on unpkg3725if (!easyedaBrowserPromise) {
L3726: easyedaBrowserPromise = import(
L3727: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-O7UDYGZW.jsView on unpkg · L3725Findings
1 Critical6 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-O7UDYGZW.js
MediumDynamic Requiredist/chunk-O7UDYGZW.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 Dependency Evidencepackage.json
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3046.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3046 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.