teammesh@0.19.0
⚠ Under reviewTeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe inspected JavaScript shows a conditional native CLI setup and argument forwarding, but does not establish an attack. Because the CLI executes bundled native binaries that could not be adequately inspected, their behavior remains materially unresolved.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing with npm may replace the JavaScript shim; running tm invokes the matching native binary.
Impact
The behavior and effects of the invoked native CLI could not be established from the available source inspection.
Mechanism
The postinstall script stages a native binary and tests its version command before replacing the shim. The shim then forwards arguments to that binary.
AI rationale
The inspected JavaScript shows a conditional native CLI setup and argument forwarding, but does not establish an attack. Because the CLI executes bundled native binaries that could not be adequately inspected, their behavior remains materially unresolved.
Evidence
native/win32-arm64/tm.exenative/linux-arm64/tmnative/darwin-x64/tmnative/win32-x64/tm.exenative/darwin-arm64/tmnative/linux-x64/tmbin/tm.js
Decision evidence
public snapshotAI called this Manual Review at 96.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json runs install.js from a postinstall hook; install.js can replace the CLI shim with a native executable.
- bin/tm.js forwards the CLI invocation and arguments to the platform-specific native binary.
- The offline analyses could not inspect several native binaries; the x64 Windows analysis also leaves call targets unresolved.
Evidence against
- The inspected JavaScript install path conditionally stages a matching binary, checks it with --version, and replaces the shim only if that succeeds.
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 unpkg14"bin": {
"tm": "bin/tm.js"
},
"scripts": {
"postinstall": "node install.js"
},
"files": [
Low
Suspicious Lifecycle Evidence
package.json runs install.js from a postinstall hook; install.js can replace the CLI shim with a native executable.
package.jsonView on unpkg · L14native/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
LowAi Review Evidencebin/tm.js
LowAi Review Evidence.lpm-inspection-mufjMr/0-dab5fc04de75.txt
Affected versions and remediation
This report applies to teammesh@0.19.0.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.19.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.