teammesh@0.1.2
⚠ Under reviewTeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe source shows that the CLI runs shipped native executables, but offline analysis leaves their behavior unresolved. This does not establish malicious behavior; manual review is appropriate because the native program is the active CLI implementation.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the package with lifecycle scripts enabled or invoking the `tm` CLI.
Impact
The native program’s effects cannot be determined from the inspected source and available offline analysis.
Mechanism
The postinstall may replace the CLI shim with a native executable, and the shim launches the platform-specific executable with the supplied arguments.
AI rationale
The source shows that the CLI runs shipped native executables, but offline analysis leaves their behavior unresolved. This does not establish malicious behavior; manual review is appropriate because the native program is the active CLI implementation.
Evidence
.lpm-inspection-arbfc5/1-95ebfb4d7cf4.txt.lpm-inspection-arbfc5/3-281211c34d69.txt.lpm-inspection-arbfc5/0-2d82716e4d11.txtinstall.jsbin/tm.jsnative/linux-arm64/tmnative/win32-x64/tm.exenative/win32-arm64/tm.exe
Decision evidence
public snapshotAI called this Manual Review at 95.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The package runs `install.js` during postinstall.
- The installer may replace the CLI shim with a native executable after checking that it runs.
- The CLI passes its arguments to the platform-specific native executable.
- Offline analysis could not inspect the Linux ARM64 executable’s behavior.
- The Windows x64 analysis leaves native call targets uninspected.
- The Windows ARM64 executable’s inspection failed.
Evidence against
- The installer exits on Windows and when npm is not the package manager.
- The installer removes the staged file if the native executable check or 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 unpkg18"postinstall": "node install.js"
},
"files": [
"bin",
"native",
"install.js",
"LICENSE"
],
"engines": {
"node": ">=18"
}
}
Low
Suspicious Lifecycle Evidence
The package runs `install.js` during postinstall.
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
LowAi Review Evidenceinstall.js
LowAi Review Evidencebin/tm.js
LowAi Review Evidence.lpm-inspection-arbfc5/1-95ebfb4d7cf4.txt
Affected versions and remediation
This report applies to teammesh@0.1.2.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.1.2 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.