teammesh@0.19.1
⚠ Under reviewTeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe JavaScript installer and launcher show ordinary binary setup and command forwarding, but the native CLI is the package’s primary runtime and its behavior remains materially unresolved. Manual review is needed to assess those binaries.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing with npm may stage a platform binary; invoking the CLI runs the matching binary.
Impact
The native CLI behavior remains unresolved, so its effects cannot be established from inspected source.
Mechanism
The installer can replace the JavaScript shim with a native executable, and the shim forwards CLI arguments to that executable.
AI rationale
The JavaScript installer and launcher show ordinary binary setup and command forwarding, but the native CLI is the package’s primary runtime and its behavior remains materially unresolved. Manual review is needed to assess those binaries.
Evidence
.lpm-inspection-9i0jW5/1-3ce77fe2b2bc.txt.lpm-inspection-9i0jW5/3-811ec985ed00.txtinstall.jsbin/tm.jsnative/linux-arm64/tmnative/win32-x64/tm.exe
Decision evidence
public snapshotAI called this Manual Review at 86.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The postinstall runs an installer that conditionally stages the platform binary and replaces the CLI shim after a version check.
- The CLI shim launches the matching native binary and forwards its arguments.
- Offline analysis could not resolve behavior in the Linux ARM binary or fully inspect the Windows x64 binary.
Evidence against
- The installer exits on Windows and when the package manager is not npm.
- The installer only replaces the shim after the staged binary runs with --version.
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"
Low
Suspicious Lifecycle Evidence
The postinstall runs an installer that conditionally stages the platform binary and replaces the CLI shim after a version check.
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 Evidenceinstall.js
LowAi Review Evidencebin/tm.js
Affected versions and remediation
This report applies to teammesh@0.19.1.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.19.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.