teammesh@0.6.0
⚠ Under reviewTeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe readable install and launcher code show a platform-specific binary setup and dispatch, but do not establish an attack. The shipped native executables contain the CLI behavior and could not be adequately inspected, so the risk remains unresolved.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the teammesh CLI invokes the native executable; npm installation may replace the JavaScript shim with that executable.
Impact
Unknown; the native program is the main unresolved behavior.
Mechanism
The launcher selects the executable for the current platform and forwards CLI arguments. Its native behavior could not be assessed from the available inspection.
AI rationale
The readable install and launcher code show a platform-specific binary setup and dispatch, but do not establish an attack. The shipped native executables contain the CLI behavior and could not be adequately inspected, so the risk remains unresolved.
Evidence
.lpm-inspection-164BtR/5-d8b0609d2ef5.txt.lpm-inspection-164BtR/3-22c211a1e749.txtpackage.jsoninstall.jsbin/tm.jsnative/linux-x64/tmnative/win32-x64/tm.exe
Decision evidence
public snapshotAI called this Manual Review at 96.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The postinstall hook installs a platform-specific native executable, and the launcher runs it with the supplied arguments.
- Offline analysis could not inspect the Linux executable and left its behavior unresolved; Windows analysis also left native call targets uninspected.
Evidence against
- The postinstall script only attempts a binary replacement for npm on non-Windows platforms, and keeps the JavaScript shim if replacement fails.
- The launcher passes command-line arguments through to the native executable; the inspected JavaScript does not establish malicious behavior.
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 unpkg18"postinstall": "node install.js"
},
"files": [
"bin",
"native",
"install.js",
"LICENSE"
],
"engi
Low
Suspicious Lifecycle Evidence
The postinstall hook installs a platform-specific native executable, and the launcher runs it with the supplied arguments.
package.jsonView on unpkg · L18native/win32-arm64/tm.exeView file
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 Evidencepackage.json
LowSuspicious Lifecycle Evidenceinstall.js
LowSuspicious Lifecycle Evidencebin/tm.js
LowSuspicious Lifecycle Evidence.lpm-inspection-164BtR/5-d8b0609d2ef5.txt
Affected versions and remediation
This report applies to teammesh@0.6.0.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.6.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.