teammesh@0.41.0
TeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package’s install hook visibly validates and installs its own CLI binary, which is consistent with its purpose. The bundled native binary appears to include Sentry crash reporting, but the available analysis cannot establish whether it is opt-in or what data it sends, so I’m flagging a runtime telemetry concern.
Static reason
One or more suspicious static signals were detected.
Trigger
Potentially during CLI runtime or crash handling; whether reporting runs by default is unresolved.
Impact
Crash diagnostics may be sent to Sentry; the included analysis does not establish what data is collected.
Mechanism
The native binary analysis includes a Sentry ingestion endpoint and a `TM_CRASH_REPORTS` setting.
AI rationale
The package’s install hook visibly validates and installs its own CLI binary, which is consistent with its purpose. The bundled native binary appears to include Sentry crash reporting, but the available analysis cannot establish whether it is opt-in or what data it sends, so I’m flagging a runtime telemetry concern.
Evidence
.lpm-inspection-ZKW855/5-281eae29984b.txtnative/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 66.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The Windows x64 native binary analysis contains a Sentry ingestion URL and the `TM_CRASH_REPORTS` setting.
- The native binary analysis also contains TeamMesh API and sync service URLs, consistent with the CLI’s stated purpose.
- The package routes the `tm` command through a platform-specific native binary.
- The postinstall hook runs the staged binary with `--version` before replacing the JavaScript shim.
Evidence against
- The postinstall hook is conditional on platform and npm, and its visible actions are copying, validating, and replacing the CLI shim.
- The available native analysis does not establish whether crash reporting is enabled by default or what data it sends.
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 = 9584640
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-ZKW855/5-281eae29984b.txt
MediumAi Review Evidence.lpm-inspection-ZKW855/5-281eae29984b.txt
MediumAi Review Evidencebin/tm.js
MediumSuspicious Lifecycle Evidenceinstall.js
LowScripts Present
LowFilesystem
LowNo License
Affected versions and remediation
This report applies to teammesh@0.41.0.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.41.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.