teammesh@0.31.0
TeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe readable install code stages a platform-specific CLI, checks that it runs with --version, and then replaces the JavaScript shim. The binary inspection found TeamMesh service endpoints and a Sentry crash-reporting string, but no evidence of malicious collection or actions; opaque native code limits certainty.
Static reason
One or more suspicious static signals were detected.
Trigger
npm postinstall on non-Windows platforms; otherwise, when the user invokes tm.
Impact
No harmful behavior was established from the readable source or bounded binary analysis. Several native builds remain opaque, and the Sentry reporting behavior could not be determined.
Mechanism
The hook copies the matching packaged executable, runs it with --version, then replaces bin/tm.js if it succeeds. The JavaScript CLI wrapper forwards arguments to that executable.
AI rationale
The readable install code stages a platform-specific CLI, checks that it runs with --version, and then replaces the JavaScript shim. The binary inspection found TeamMesh service endpoints and a Sentry crash-reporting string, but no evidence of malicious collection or actions; opaque native code limits certainty.
Evidence
bin/tm.jsbin/tm.js.native
Network endpoints3
api.teammesh.iosync.teammesh.io39a18618b3abf2d4bee26b2b5fefc1d6@o4512288884326400.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Clean at 76.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook only runs for npm on non-Windows platforms and checks whether a platform binary exists.
- The installer stages that binary, runs it with --version, and replaces the CLI shim only if the check succeeds.
- The CLI wrapper runs the matching packaged native binary with the user's arguments.
- The inspected binary strings name TeamMesh API and sync hosts and a Sentry crash-reporting endpoint; no credential theft or unrelated collector behavior was established.
Evidence against
- The native executables are the core CLI and several platform builds could not be structurally inspected.
- The postinstall hook executes the native binary automatically to validate it.
- The binary strings include a Sentry endpoint and a TM_CRASH_REPORTS setting, but the available analysis does not establish when reports are sent or what they contain.
Behavioral surface
ChildProcessEnvironmentVarsFilesystem
Source & flagged code
7 flaggedpackage.jsonView file
•scripts.postinstall = node install.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node install.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgnative/win32-arm64/tm.exeView file
•path = native/win32-arm64/tm.exe
kind = native_binary
sizeBytes = 9404928
magicHex = [redacted]
Medium
Findings
1 High4 Medium7 Low
HighInstall Time Lifecycle Scriptspackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumShips Native Binarynative/win32-arm64/tm.exe
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowNo License
LowSuspicious Lifecycle Evidenceinstall.js
LowAi Review Evidenceinstall.js
LowAi Review Evidencebin/tm.js
LowAi Review Evidence.lpm-inspection-qA4WUZ/5-541a0c3ba6b3.txt
Affected versions and remediation
This report applies to teammesh@0.31.0.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.31.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.