teammesh@0.24.2
⚠ Under reviewTeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe inspected JavaScript establishes that the CLI delegates execution to bundled native binaries. Offline analysis could not resolve behavior for several platform binaries and left the Windows x64 call graph incomplete, so a clean or malicious verdict is not supported by the available source evidence.
Static reason
One or more suspicious static signals were detected.
Trigger
An npm installation may replace the CLI shim with a native binary; running the CLI then launches that binary.
Impact
The native executable's behavior could not be sufficiently assessed, so its effects remain unknown.
Mechanism
The postinstall probes a staged platform binary and swaps it into the CLI path. The shim forwards CLI arguments to the native executable.
AI rationale
The inspected JavaScript establishes that the CLI delegates execution to bundled native binaries. Offline analysis could not resolve behavior for several platform binaries and left the Windows x64 call graph incomplete, so a clean or malicious verdict is not supported by the available source evidence.
Evidence
package.jsoninstall.jsbin/tm.js.lpm-inspection-jPApLN/0-37cffaa6f9c4.txt.lpm-inspection-jPApLN/1-022949cbce35.txt.lpm-inspection-jPApLN/2-0963b0a76a50.txt.lpm-inspection-jPApLN/3-5240f53d9b09.txt.lpm-inspection-jPApLN/4-42b8b3050d47.txt.lpm-inspection-jPApLN/5-6e971bdbeab2.txt
Decision evidence
public snapshotAI called this Manual Review at 91.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json runs install.js from an npm postinstall hook.
- install.js probes the staged native binary, then replaces the CLI shim with it.
- bin/tm.js launches the platform-specific native binary with the CLI arguments.
- The Linux and macOS native analyses report that executable behavior remains unresolved.
- The Windows ARM64 binary is unsupported by the analysis, and the Windows x64 call graph is incomplete.
Evidence against
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"
],
"engines": {
"node": ">=18"
}
}
Low
Suspicious Lifecycle Evidence
package.json runs install.js from an npm 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-jPApLN/1-022949cbce35.txt
Affected versions and remediation
This report applies to teammesh@0.24.2.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.24.2 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.