@t2code/cli@0.0.39
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe CLI sends default-on runtime analytics to PostHog, including usage metadata and a pseudonymous identifier. The source provides a disable setting, but user-facing disclosure is not established, so this is suspicious telemetry rather than evidence of credential theft or malicious exfiltration.
Decision evidence
public snapshot- Runtime PostHog telemetry is enabled by default and can be redirected through configuration.
- Telemetry sends an installation identifier and platform, architecture, app version, and client type to PostHog.
- The identifier may be derived by hashing a Codex or Claude account ID.
- Usage events include provider, model, interaction mode, attachment count, and whether input was present; no prompt text is shown in the inspected event.
- The telemetry code describes the identifier as anonymous and provides a T3CODE_TELEMETRY_ENABLED setting to disable collection.
- The inspected usage event sends metadata and a Boolean input-presence flag, not the input itself.
- The CLI starts only when its entry point is invoked.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/NodeServices-dtFYIkeJ.mjsView on unpkg · L6Source spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.
dist/NodeServices-dtFYIkeJ.mjsView on unpkg · L6Findings
Affected versions and remediation
This report applies to @t2code/cli@0.0.39.
See all versions of @t2code/cli for other recorded verdicts.
- Review the evidence and your use of @t2code/cli@0.0.39 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.