teammesh@0.10.0
⚠ Under reviewTeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 17d ago · by lpm-firewall-aiThe JavaScript install and launcher path is understandable, but it activates shipped native code that the available analyses do not adequately resolve. Because that code is central to normal CLI operation, manual review is needed to determine its behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing with npm may stage a platform binary; invoking the CLI runs the selected platform binary.
Impact
The native executable's behavior and effects remain unknown, so the package's runtime impact cannot be determined from the inspected evidence.
Mechanism
The installer may replace the JavaScript shim with a native executable, and the shim launches that executable with the supplied arguments.
AI rationale
The JavaScript install and launcher path is understandable, but it activates shipped native code that the available analyses do not adequately resolve. Because that code is central to normal CLI operation, manual review is needed to determine its behavior.
Evidence
.lpm-inspection-BxewVk/5-020f725d3505.txt.lpm-inspection-BxewVk/3-9432ef83c3bb.txt.lpm-inspection-BxewVk/0-3baa149ecc35.txtpackage.jsoninstall.jsbin/tm.js
Decision evidence
public snapshotAI called this Manual Review at 88.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest defines a postinstall hook that runs the installer and exposes the CLI through a JavaScript shim.
- The installer can replace the shim with a platform binary, and the shim executes that binary with the user's arguments.
- Offline analysis could not resolve the behavior of the Linux binary; analysis of the Windows x64 binary also leaves targets uninspected.
Evidence against
- The installer only attempts the replacement for npm on non-Windows systems, checks that the binary runs, and removes the staged copy if replacement 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 unpkg14"bin": {
"tm": "bin/tm.js"
},
"scripts": {
"postinstall": "node install.js"
},
"files": [
"bi
Low
Suspicious Lifecycle Evidence
The manifest defines a postinstall hook that runs the installer and exposes the CLI through a JavaScript shim.
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-BxewVk/5-020f725d3505.txt
Affected versions and remediation
This report applies to teammesh@0.10.0.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.10.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.