@adithyasak/t3@0.0.38-adi.4
AI Security Review
scanned 2mo ago · by lpm-firewall-aiStatic inspection found no lifecycle hook, automatic payload execution, or credential-harvesting path. Scanner findings correspond to normal CLI, PTY, and opt-in relay functionality.
Decision evidence
public snapshot- The manifest exposes a CLI entry point and contains no lifecycle scripts.
- The CLI runs only when its file is the process entry point.
- The flagged Node and Bun files are PTY and child-process adapters for commands supplied to the CLI.
- Remote linking is exposed as an explicit `t3 connect` command; startup reconciliation requires previously stored opt-in state.
- No install-time or import-time execution was found.
- No source path was found harvesting local credentials or sending environment variables to an unrelated endpoint.
- The relay uses authenticated, configured cloud-link requests rather than an automatic exfiltration path.
Source & flagged code
22 flaggedSource archives sensitive local configuration and publishes encoded chunks through an authenticated package-registry request.
dist/bin.mjsView on unpkg · L3Findings
Affected versions and remediation
This report applies to @adithyasak/t3@0.0.38-adi.4.
See all versions of @adithyasak/t3 for other recorded verdicts.
- Review the evidence and your use of @adithyasak/t3@0.0.38-adi.4 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.