teammesh@0.29.1
⚠ Under reviewTeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 11d ago · by lpm-firewall-aiThe JavaScript install and launch paths are visible, but execution is handed to bundled native binaries that the available analyses leave unresolved or only partially inspected. The evidence does not establish a concrete attack, so the native runtime requires manual review.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation runs the postinstall hook; later CLI use launches the matching native binary.
Impact
The native executable can perform the CLI's runtime actions, but those actions could not be assessed from the available analysis.
Mechanism
The hook stages a native binary as the CLI shim, and the shim forwards command-line arguments to it.
AI rationale
The JavaScript install and launch paths are visible, but execution is handed to bundled native binaries that the available analyses leave unresolved or only partially inspected. The evidence does not establish a concrete attack, so the native runtime requires manual review.
Evidence
.lpm-inspection-mMzth3/0-5add2d021fe9.txt.lpm-inspection-mMzth3/1-343c74764d5a.txt.lpm-inspection-mMzth3/2-c3c6d79774cc.txt.lpm-inspection-mMzth3/3-db361e40a5f1.txt.lpm-inspection-mMzth3/4-8b3bd90c4e12.txt.lpm-inspection-mMzth3/5-7581bee3b066.txtinstall.jsbin/tm.jsnative/win32-arm64/tm.exenative/linux-arm64/tmnative/darwin-x64/tmnative/win32-x64/tm.exenative/darwin-arm64/tmnative/linux-x64/tm
Decision evidence
public snapshotAI called this Manual Review at 91.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The postinstall hook runs install.js.
- The hook stages a bundled native binary and replaces the CLI shim after checking that the binary runs.
- The CLI shim forwards its arguments to the native executable.
- The native analyses leave platform binaries unresolved or only partially inspected, so their runtime behavior cannot be cleared from source.
Evidence against
- The install hook exits on Windows and when the npm user agent check does not pass; it also skips platforms without a matching binary.
- The inspected JavaScript contains no confirmed credential transfer or unrelated network request.
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"
},
Low
native/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-mMzth3/0-5add2d021fe9.txt
Affected versions and remediation
This report applies to teammesh@0.29.1.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.29.1 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.