teammesh@0.27.0
TeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe inspected installer and launcher show a version-checked native-binary handoff, but the shipped executables are the primary runtime and several could not be analyzed. This unresolved behavior warrants a warning; the available source does not establish a concrete attack.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation through npm on a supported non-Windows platform can replace the launcher; invoking the CLI then runs the native executable.
Impact
The native program's behavior cannot be established from the available offline analyses, so potential effects remain unknown.
Mechanism
The install hook copies a platform executable over the JavaScript launcher after a version check, and the launcher passes CLI arguments to that executable.
AI rationale
The inspected installer and launcher show a version-checked native-binary handoff, but the shipped executables are the primary runtime and several could not be analyzed. This unresolved behavior warrants a warning; the available source does not establish a concrete attack.
Evidence
package.jsoninstall.jsbin/tm.js.lpm-inspection-Sr0DEm/0-08c7ee7c6d79.txt.lpm-inspection-Sr0DEm/1-2a68fa73928c.txt.lpm-inspection-Sr0DEm/2-b579cd997bd4.txt.lpm-inspection-Sr0DEm/3-d3b939569464.txt.lpm-inspection-Sr0DEm/4-ff02886c0e1d.txt.lpm-inspection-Sr0DEm/5-52eb282ba22f.txt
Decision evidence
public snapshotAI called this Suspicious at 80.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The manifest runs install.js as a postinstall hook.
- The hook can replace the JavaScript launcher with a native executable, and the launcher runs that executable when invoked.
- The shipped native executables could not be fully inspected, leaving their behavior unresolved.
Evidence against
- The install hook checks the staged executable with a version command before replacing the launcher and removes the staged copy if that check fails.
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"
}
}
Medium
Suspicious Lifecycle Evidence
The manifest runs install.js as a postinstall hook.
package.jsonView on unpkg · L18native/win32-arm64/tm.exeView file
Findings
1 High8 Medium3 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
MediumSuspicious Lifecycle Evidencepackage.json
MediumAi Review Evidenceinstall.js
MediumAi Review Evidenceinstall.js
MediumAi Review Evidencebin/tm.js
LowScripts Present
LowFilesystem
LowNo License
Affected versions and remediation
This report applies to teammesh@0.27.0.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.27.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.