teammesh@0.45.0
TeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 22h ago · by lpm-firewall-aiThe install hook performs a local replacement with the package's bundled CLI, and the JavaScript entry point only launches that binary with the user's arguments. The native binaries are largely unreadable in the supplied analysis, but the available evidence does not establish malicious or otherwise suspicious behavior.
Decision evidence
public snapshot- The package describes itself as a TeamMesh CLI for connecting AI coding agents to a team.
- The postinstall script locally replaces the JavaScript shim with a matching bundled native binary; it makes no network request.
- The CLI wrapper selects and runs the bundled platform binary with the user's arguments.
- Readable binary strings name TeamMesh API and sync hosts, plus a Sentry crash-reporting DSN; the available view does not establish what data is sent or when.
- The postinstall hook modifies bin/tm.js and executes the staged binary with --version, so install-time execution is present.
- Most native binaries could not be meaningfully inspected, and the Windows x64 analysis is explicitly limited.
Source & flagged code
7 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgThe package describes itself as a TeamMesh CLI for connecting AI coding agents to a team.
package.jsonView on unpkg · L2Findings
Affected versions and remediation
This report applies to teammesh@0.45.0.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.45.0 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.