@adithyasak/t3@0.0.39-adi.1
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe source enables runtime telemetry by default, including a persistent hashed identifier derived from local Codex or Claude account IDs. I found no clear user-facing disclosure in the inspected package files, so this merits a warning rather than a block.
Decision evidence
public snapshot- The package exposes a CLI and declares no lifecycle scripts in its manifest.
- Runtime PostHog telemetry is enabled by default and can be disabled with T3CODE_TELEMETRY_ENABLED.
- Telemetry sends an identifier and usage events with platform, architecture, version, and client type to PostHog.
- The identifier can be derived by hashing a Codex account ID or Claude user ID; startup telemetry reports thread and project counts.
- The inspected manifest has no install, preinstall, or postinstall hook.
- The inspected telemetry payload contains usage and platform fields; I found no credential forwarding to an unrelated host.
Source & flagged code
10 flaggedPackage source references child process execution.
dist/service-launcher.mjsView on unpkg · L2Package source references dynamic require/import behavior.
dist/client/assets/typescript-S0auFSj_.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @adithyasak/t3@0.0.39-adi.1.
See all versions of @adithyasak/t3 for other recorded verdicts.
- Review the evidence and your use of @adithyasak/t3@0.0.39-adi.1 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.