teammesh@0.34.4
⚠ Under reviewTeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe install hook appears limited to staging and validating the package's own native CLI before replacing its shim. Because the native executable is the package's core behavior and its analysis leaves important call targets uninspected, the available source does not support a firm clean or malicious verdict.
Static reason
One or more suspicious static signals were detected.
Trigger
The postinstall script validates the binary with --version; later, running tm launches that binary.
Impact
The available evidence is insufficient to determine what the native CLI collects or sends, so a security verdict requires review of the binary behavior.
Mechanism
The JavaScript shim delegates all CLI arguments to a platform-specific executable. Analysis strings reference TeamMesh service hosts and a Sentry crash-reporting endpoint, but do not establish data flows.
AI rationale
The install hook appears limited to staging and validating the package's own native CLI before replacing its shim. Because the native executable is the package's core behavior and its analysis leaves important call targets uninspected, the available source does not support a firm clean or malicious verdict.
Evidence
install.jsbin/tm.jsnative/win32-x64/tm.exe.lpm-inspection-Hwgrdj/5-1a2f5c2a72cc.txtbin/tm.js.native
Network endpoints3
api.teammesh.iosync.teammesh.ioo4512288884326400.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Manual Review at 78.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The postinstall script stages the platform binary, checks it with --version, and replaces the CLI shim.
- The CLI shim launches the platform-specific native executable with the user's arguments.
- The available native analysis reports that disassembly exceeded its output budget and that indirect calls remain uninspected.
- The native analysis contains strings naming TeamMesh API and sync hosts and a Sentry crash-reporting endpoint, but does not show what data is sent or when.
Evidence against
- The install script does not download code or contact a network host in the inspected JavaScript.
- The endpoint strings are consistent with a TeamMesh CLI and crash reporting, but their behavior could not be confirmed.
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 = 9455104
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
LowSuspicious Lifecycle Evidenceinstall.js
LowAi Review Evidencebin/tm.js
LowAi Review Evidence.lpm-inspection-Hwgrdj/5-1a2f5c2a72cc.txt
Affected versions and remediation
This report applies to teammesh@0.34.4.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.34.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.