teammesh@0.34.5
TeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe native CLI contains a Sentry reporting endpoint and a related environment-variable name, but the available binary analysis cannot establish the default behavior or report contents. This leaves a runtime telemetry risk that warrants warning rather than a block; the visible install hook only stages and checks the CLI binary.
Static reason
One or more suspicious static signals were detected.
Trigger
Unknown; potentially when the native CLI encounters a reportable crash. The package’s shim invokes the binary when a user runs tm.
Impact
If enabled by default, crash data may be sent to Sentry without user awareness; the contents and sensitivity of any report are undetermined.
Mechanism
The native binary contains a Sentry ingest DSN and the TM_CRASH_REPORTS environment-variable name. The binary analysis is limited and does not show whether reporting is enabled by default, what it transmits, or how the setting works.
AI rationale
The native CLI contains a Sentry reporting endpoint and a related environment-variable name, but the available binary analysis cannot establish the default behavior or report contents. This leaves a runtime telemetry risk that warrants warning rather than a block; the visible install hook only stages and checks the CLI binary.
Evidence
native/win32-x64/tm.exeinstall.jsbin/tm.js
Network endpoints3
o4512288884326400.ingest.us.sentry.ioapi.teammesh.iosync.teammesh.io
Decision evidence
public snapshotAI called this Suspicious at 72.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The limited native-binary analysis shows a Sentry ingest DSN alongside the TM_CRASH_REPORTS environment-variable name, but does not establish whether reporting is enabled by default or what data it sends.
- The postinstall hook runs the native CLI with --version and replaces bin/tm.js with that binary; the JavaScript shim forwards user-supplied arguments to the binary.
Evidence against
- The installer’s visible code only copies and checks the platform binary, replaces the shim, and optionally prints an upgrade notice; no network request or data collection is visible there.
- The CLI’s embedded service URLs are api.teammesh.io and sync.teammesh.io, consistent with the package’s stated purpose of connecting AI coding agents to a team.
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 unpkgnative/win32-arm64/tm.exeView file
•path = native/win32-arm64/tm.exe
kind = native_binary
sizeBytes = 9454080
magicHex = [redacted]
Medium
Findings
1 High8 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-kzUiaL/5-17ace23a679d.txt
MediumSuspicious Lifecycle Evidenceinstall.js
MediumSuspicious Lifecycle Evidencebin/tm.js
MediumSuspicious Lifecycle Evidence.lpm-inspection-kzUiaL/5-17ace23a679d.txt
LowScripts Present
LowFilesystem
LowNo License
Affected versions and remediation
This report applies to teammesh@0.34.5.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.34.5 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.