teammesh@0.32.1
TeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 6d ago · by lpm-firewall-aiStatic analysis of the bundled native CLI indicates Sentry crash-reporting integration, while the package provides no readable disclosure of its default or transmitted data. The evidence does not establish that reports are sent automatically, so this is a telemetry warning rather than a confirmed attack.
Static reason
One or more suspicious static signals were detected.
Trigger
Potentially during native CLI runtime; the package does not establish the reporting trigger or default setting in its readable JavaScript source.
Impact
If enabled without user awareness, crash reports may send runtime data to the Sentry endpoint.
Mechanism
The native binary contains a Sentry ingestion URL and a `TM_CRASH_REPORTS` string.
AI rationale
Static analysis of the bundled native CLI indicates Sentry crash-reporting integration, while the package provides no readable disclosure of its default or transmitted data. The evidence does not establish that reports are sent automatically, so this is a telemetry warning rather than a confirmed attack.
Evidence
.lpm-inspection-3ytbHp/5-f58fc1b5729c.txtinstall.jsbin/tm.js.nativebin/tm.js
Network endpoints1
o4512288884326400.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Suspicious at 73.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The native Windows CLI analysis contains a Sentry ingestion URL and the `TM_CRASH_REPORTS` string, indicating crash-reporting integration; it does not establish the default setting or report contents.
- The postinstall script runs the package’s own platform binary with `--version` before replacing the CLI shim.
Evidence against
- The manifest describes a TeamMesh CLI, and the JavaScript launcher forwards command-line arguments to its matching native binary.
- The inspected install script copies and tests a bundled binary; it contains no explicit network request or collection of host, user, or project data.
Behavioral surface
ChildProcessEnvironmentVarsFilesystem
NoLicense
Source & flagged code
5 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 unpkgnative/win32-arm64/tm.exeView file
•path = native/win32-arm64/tm.exe
kind = native_binary
sizeBytes = 9426944
magicHex = [redacted]
Medium
Findings
1 High6 Medium3 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
MediumAi Review Evidence.lpm-inspection-3ytbHp/5-f58fc1b5729c.txt
MediumSuspicious Lifecycle Evidenceinstall.js
LowScripts Present
LowFilesystem
LowNo License
Affected versions and remediation
This report applies to teammesh@0.32.1.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.32.1 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.