teammesh@0.26.2
⚠ Under reviewTeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe inspected JavaScript establishes a postinstall path to bundled native code, and the CLI executes that code for user commands. The available analyses leave native behavior unresolved, so this review cannot determine whether the package is malicious.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing through npm on a supported platform can replace the CLI shim; running the CLI then starts the native binary.
Impact
The native program’s runtime effects remain unknown, so the package’s behavior cannot be cleared from the inspected evidence.
Mechanism
The postinstall stages and tests a platform binary before replacing the package’s own shim, which forwards later CLI arguments to that binary.
AI rationale
The inspected JavaScript establishes a postinstall path to bundled native code, and the CLI executes that code for user commands. The available analyses leave native behavior unresolved, so this review cannot determine whether the package is malicious.
Evidence
package.jsoninstall.jsbin/tm.js.lpm-inspection-mAF6sM/3-999877d8ae20.txt.lpm-inspection-mAF6sM/5-ea9cf7ef5eba.txt
Decision evidence
public snapshotAI called this Manual Review at 91.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The package runs install.js from its postinstall hook.
- On supported installs, install.js runs the staged native binary and replaces the package’s CLI shim with it.
- The CLI shim passes its arguments to the native binary, whose behavior remains unresolved in the available artifact analyses.
Evidence against
- The inspected JavaScript shows the postinstall changing the package’s own CLI shim; it does not establish a broader filesystem mutation or a confirmed attack.
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 from its 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-mAF6sM/3-999877d8ae20.txt
Affected versions and remediation
This report applies to teammesh@0.26.2.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.26.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.