teammesh@0.2.0
⚠ Under reviewTeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe source shows a conditional install-time native execution path and runtime delegation to shipped binaries, while offline inspection leaves their behavior unresolved. This does not establish malicious behavior, so manual review is warranted.
Static reason
One or more suspicious static signals were detected.
Trigger
Installation through npm on a non-Windows platform runs the installer; invoking tm launches the platform binary.
Impact
The effects of the native executable remain unknown, including during its installation-time version check.
Mechanism
The installer stages the binary, runs it with --version, and may replace bin/tm.js. The CLI shim launches the native binary with the supplied arguments.
AI rationale
The source shows a conditional install-time native execution path and runtime delegation to shipped binaries, while offline inspection leaves their behavior unresolved. This does not establish malicious behavior, so manual review is warranted.
Evidence
.lpm-inspection-XwwyuC/5-f5668206c889.txt.lpm-inspection-XwwyuC/3-8ac2942f0d70.txt.lpm-inspection-XwwyuC/1-b25e79e83bda.txtpackage.jsoninstall.jsbin/tm.jsnative/linux-x64/tmnative/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
- package.json runs install.js during postinstall.
- install.js selects a platform binary, copies it over the CLI shim, and runs it with --version during installation.
- bin/tm.js launches the platform binary with the CLI arguments and inherited input/output.
- The inspected Linux and Windows native analyses leave executable behavior unresolved.
Evidence against
- The installer skips Windows and non-npm installs, and removes the staged copy if its check fails.
- The installer describes the shim replacement as a startup optimization for the CLI.
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 unpkg17"scripts": {
"postinstall": "node install.js"
},
"files": [
"bin",
"native",
"
Low
Suspicious Lifecycle Evidence
package.json runs install.js during postinstall.
package.jsonView on unpkg · L17native/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 Evidenceinstall.js
LowAi Review Evidenceinstall.js
Affected versions and remediation
This report applies to teammesh@0.2.0.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.2.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.