teammesh@0.40.0
TeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe install hook only stages and validates a bundled executable, and the JavaScript entry point forwards user-supplied arguments to that CLI. The native executable is opaque, but the available evidence does not establish malicious behavior or an unrelated collection flow.
Static reason
One or more suspicious static signals were detected.
Trigger
The postinstall hook stages the bundled CLI binary for eligible npm installs; users run the CLI through its JavaScript shim.
Impact
No malicious or unauthorized effect was established from the available source evidence.
Mechanism
The hook copies and validates the package's bundled binary. The shim forwards CLI arguments to that binary. Readable binary strings name TeamMesh service endpoints and a Sentry endpoint, but do not establish the behavior that uses them.
AI rationale
The install hook only stages and validates a bundled executable, and the JavaScript entry point forwards user-supplied arguments to that CLI. The native executable is opaque, but the available evidence does not establish malicious behavior or an unrelated collection flow.
Evidence
install.jsbin/tm.jsnative/win32-x64/tm.exe
Network endpoints3
api.teammesh.iosync.teammesh.ioo4512288884326400.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Clean at 78.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook stages a bundled platform binary and checks that it runs; no install-time network call appears in the hook.
- The JavaScript CLI selects the matching bundled binary and forwards the user's arguments to it.
- The native-binary strings name TeamMesh service endpoints and a Sentry endpoint; the package describes itself as a CLI connecting AI coding agents to a team.
Evidence against
- The native executable is opaque; its runtime behavior and the conditions for Sentry reporting could not be verified from the readable binary view.
Behavioral surface
ChildProcessEnvironmentVarsFilesystem
NoLicense
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 = 9580032
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 Evidencebin/tm.js
LowAi Review Evidence.lpm-inspection-hMeKkw/5-2b69fc9f0005.txt
LowAi Review Evidence.lpm-inspection-hMeKkw/5-2b69fc9f0005.txt
Affected versions and remediation
This report applies to teammesh@0.40.0.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.40.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.