teammesh@0.11.0
⚠ Under reviewTeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 17d ago · by lpm-firewall-aiThe inspected JavaScript shows a platform-gated native binary replacement and execution path, but does not establish malicious behavior. Because analysis leaves several active binaries materially unresolved, manual review is warranted.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation or running the tm CLI on a platform with a shipped binary.
Impact
The native program's effects remain unknown, leaving a material gap in the active install and runtime paths.
Mechanism
The install hook tests and swaps in the native binary; the CLI shim then passes it the user's arguments.
AI rationale
The inspected JavaScript shows a platform-gated native binary replacement and execution path, but does not establish malicious behavior. Because analysis leaves several active binaries materially unresolved, manual review is warranted.
Evidence
.lpm-inspection-2ZyWS8/0-f6d36ecef3ab.txt.lpm-inspection-2ZyWS8/1-7fd50731943c.txt.lpm-inspection-2ZyWS8/2-4411b0125d45.txt.lpm-inspection-2ZyWS8/3-fc1469e22883.txt.lpm-inspection-2ZyWS8/5-c34a036e16ce.txtpackage.jsoninstall.jsbin/tm.jsnative/linux-arm64/tmnative/darwin-x64/tmnative/linux-x64/tmnative/win32-arm64/tm.exenative/win32-x64/tm.exe
Decision evidence
public snapshotAI called this Manual Review at 88.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json activates install.js through a postinstall hook.
- install.js tests and replaces the CLI shim with a platform binary when its checks succeed.
- bin/tm.js launches the selected native binary with the CLI arguments.
- Offline analysis could not inspect the Linux ARM64, Linux x64, or macOS x64 binaries.
- The Windows ARM64 analysis could not inspect the artifact; Windows x64 analysis leaves native call targets uninspected.
- The native binaries are on active install and CLI paths, but their behavior remains unresolved.
Evidence against
- The install hook gates replacement on platform, npm user agent, binary availability, and a successful --version check.
- No concrete malicious behavior or network endpoint was established from the inspected source.
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.j
Low
Suspicious Lifecycle Evidence
package.json activates install.js through a postinstall hook.
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
LowAi Review Evidenceinstall.js
LowAi Review Evidencebin/tm.js
LowAi Review Evidence.lpm-inspection-2ZyWS8/1-7fd50731943c.txt
Affected versions and remediation
This report applies to teammesh@0.11.0.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.11.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.