teammesh@0.36.0
TeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe postinstall hook only stages and version-checks the package's own platform binary before replacing the CLI shim. The native artifacts are partly opaque and contain a Sentry crash-report marker, but the available evidence does not establish malicious or undisclosed collection.
Static reason
One or more suspicious static signals were detected.
Trigger
Postinstall runs automatically; normal CLI behavior requires a user command.
Impact
No malicious collection, unrelated network destination, or unauthorized account action was established from the reviewed source.
Mechanism
The hook stages and version-checks the platform binary before replacing `bin/tm.js`. The readable native strings name TeamMesh API/sync services and a Sentry crash-report endpoint.
AI rationale
The postinstall hook only stages and version-checks the package's own platform binary before replacing the CLI shim. The native artifacts are partly opaque and contain a Sentry crash-report marker, but the available evidence does not establish malicious or undisclosed collection.
Evidence
bin/tm.jsbin/tm.js.native
Network endpoints3
api.teammesh.iosync.teammesh.ioo4512288884326400.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Clean at 82.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes `tm` as a CLI and runs `install.js` as its postinstall hook.
- The installer skips Windows and non-npm installs.
- The installer stages the package's platform binary, checks it with `--version`, then replaces the launcher.
- The JavaScript launcher runs the matching packaged native binary with the user's supplied arguments.
- The readable binary view contains TeamMesh API and sync endpoints, plus a Sentry DSN and `TM_CRASH_REPORTS` marker; no credential theft or unrelated collector was established.
Evidence against
- Most native binaries could not be structurally analyzed; the Windows x64 view is limited.
- The native binary contains a Sentry endpoint and crash-report environment marker, but the readable view does not establish whether reporting is enabled by default.
Behavioral surface
ChildProcessEnvironmentVarsFilesystem
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 unpkg14"bin": {
"tm": "bin/tm.js"
},
"scripts": {
"postinstall": "node install.js"
},
"files": [
"bin",
"native",
Low
Suspicious Lifecycle Evidence
The manifest exposes `tm` as a CLI and runs `install.js` as its postinstall hook.
package.jsonView on unpkg · L14native/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 Evidenceinstall.js
LowAi Review Evidencebin/tm.js
Affected versions and remediation
This report applies to teammesh@0.36.0.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.36.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.