teammesh@0.3.0
⚠ Under reviewTeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 18d ago · by lpm-firewall-aiThe inspected source confirms that native executables are activated by installation and CLI use, but available analysis does not resolve their behavior. This warrants manual review; the inspected evidence does not establish a concrete attack.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation may stage and execute a native binary; later CLI use runs the platform-matched binary.
Impact
The binaries’ effects remain unknown because material portions were unsupported or uninspected.
Mechanism
The installer tests a staged native executable before replacing the JavaScript shim, and the shim forwards arguments to the binary.
AI rationale
The inspected source confirms that native executables are activated by installation and CLI use, but available analysis does not resolve their behavior. This warrants manual review; the inspected evidence does not establish a concrete attack.
Evidence
package.jsoninstall.jsbin/tm.js.lpm-inspection-mz0LWF/1-3b46cb96c5d2.txt.lpm-inspection-mz0LWF/3-d12f33fc6b3d.txt.lpm-inspection-mz0LWF/5-fc4ad4a24560.txtnative/linux-arm64/tmnative/linux-x64/tmnative/win32-x64/tm.exe
Decision evidence
public snapshotAI called this Manual Review at 88.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The postinstall hook runs the installer, which may replace the CLI shim with a native executable.
- The CLI runs the matching packaged native executable with the supplied arguments.
- The available analysis leaves native behavior unresolved: Linux binaries are unsupported, and the Windows x64 analysis is partial.
Evidence against
- The Windows x64 analysis contains a string for the TeamMesh API, consistent with the package’s stated CLI purpose, but strings alone do not establish behavior.
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 postinstall hook runs the installer, which may replace the CLI shim with a native executable.
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
LowAi Review Evidencebin/tm.js
LowAi Review Evidence.lpm-inspection-mz0LWF/3-d12f33fc6b3d.txt
Affected versions and remediation
This report applies to teammesh@0.3.0.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.3.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.