teammesh@0.25.0
⚠ Under reviewTeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe inspected JavaScript supports an installation-time native-binary check and normal CLI dispatch, but does not establish malicious behavior. Multiple shipped native executables remain unreadable or only partially analyzed, leaving material runtime behavior unresolved.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation runs the postinstall hook; later, invoking tm runs the platform-specific native executable.
Impact
The native CLI behavior cannot be assessed from the inspected source, so the package's safety remains unresolved.
Mechanism
The hook may replace the JavaScript shim with a tested native executable, and the shim forwards CLI arguments to that executable. Offline analysis could not inspect most native artifacts and left part of the Windows x64 call graph unresolved.
AI rationale
The inspected JavaScript supports an installation-time native-binary check and normal CLI dispatch, but does not establish malicious behavior. Multiple shipped native executables remain unreadable or only partially analyzed, leaving material runtime behavior unresolved.
Evidence
.lpm-inspection-ebM2yv/0-829ccc1a891e.txt.lpm-inspection-ebM2yv/1-e2e0bbedc5a4.txt.lpm-inspection-ebM2yv/2-7b3066f3ceef.txt.lpm-inspection-ebM2yv/3-8a793ef8790e.txt.lpm-inspection-ebM2yv/4-5bf04427b0f4.txt.lpm-inspection-ebM2yv/5-6b5e45a2b8bf.txtinstall.jsbin/tm.js
Decision evidence
public snapshotAI called this Manual Review at 76.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json runs install.js through a postinstall hook.
- install.js executes a bundled native binary during installation to check its version, then may replace bin/tm.js with it.
- bin/tm.js forwards CLI arguments to the platform-specific native binary.
- Offline analysis could not inspect the behavior of several shipped native binaries, and analysis of the Windows x64 binary leaves call targets unresolved.
Evidence against
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
package.json runs install.js through a postinstall hook.
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-ebM2yv/0-829ccc1a891e.txt
Affected versions and remediation
This report applies to teammesh@0.25.0.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.25.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.