teammesh@0.12.0
⚠ Under reviewTeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 17d ago · by lpm-firewall-aiThe JavaScript shows a platform-specific installer and CLI launcher, but both execute native binaries whose behavior the available analyses could not resolve. That leaves a material runtime question, so the package needs manual review rather than a clean or malicious verdict.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing with npm on a non-Windows platform runs the matching executable with --version; invoking tm runs the matching executable on supported platforms.
Impact
The native program can run during installation and normal CLI use, but its effects could not be established from the available offline analyses.
Mechanism
The install hook tests and replaces the JavaScript shim with a native executable, while the shim forwards CLI arguments to that executable.
AI rationale
The JavaScript shows a platform-specific installer and CLI launcher, but both execute native binaries whose behavior the available analyses could not resolve. That leaves a material runtime question, so the package needs manual review rather than a clean or malicious verdict.
Evidence
native/linux-x64/tm.lpm-inspection-BKejxW/5-85eb2f89915e.txtnative/linux-arm64/tm.lpm-inspection-BKejxW/1-7429d5bc7b55.txtnative/darwin-x64/tm.lpm-inspection-BKejxW/2-bd9cacd1886a.txtnative/darwin-arm64/tm.lpm-inspection-BKejxW/4-73b2cad8b82a.txtnative/win32-x64/tm.exe.lpm-inspection-BKejxW/3-01d90a13e4aa.txtnative/win32-arm64/tm.exe.lpm-inspection-BKejxW/0-31eb3d56646f.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
- package.json runs install.js after installation.
- The CLI forwards user arguments to a platform-specific native executable.
- On npm installs outside Windows, install.js runs the matching executable with --version before replacing the CLI shim.
- The supplied offline analyses could not resolve the behavior of the native executables, which the install hook and CLI run.
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
native/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
LowAi Review Evidencepackage.json
LowAi Review Evidenceinstall.js
LowAi Review Evidencebin/tm.js
LowAi Review Evidenceinstall.js
Affected versions and remediation
This report applies to teammesh@0.12.0.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.12.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.