teammesh@0.34.7
TeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe JavaScript launcher and install hook show ordinary CLI setup, but the native binary analysis reveals a Sentry crash-reporting endpoint and does not establish its default behavior or payload. Treat as suspicious telemetry pending review of the native reporting behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
Unknown; the native binary is launched by the CLI, and postinstall invokes it with `--version` and an upgrade-notice command.
Impact
If enabled by default, crash information may be sent to Sentry without clear disclosure or a confirmed opt-out.
Mechanism
The binary analysis view contains a Sentry ingest DSN and a `TM_CRASH_REPORTS` marker, but does not expose enough behavior to determine whether or how it sends reports.
AI rationale
The JavaScript launcher and install hook show ordinary CLI setup, but the native binary analysis reveals a Sentry crash-reporting endpoint and does not establish its default behavior or payload. Treat as suspicious telemetry pending review of the native reporting behavior.
Evidence
.lpm-inspection-bV7Vg1/5-54e94b47e2da.txtnative/win32-x64/tm.exeinstall.jsbin/tm.js
Network endpoints1
o4512288884326400.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Suspicious at 72.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The native binary analysis view contains a Sentry ingest DSN followed by a `TM_CRASH_REPORTS` marker, suggesting crash-reporting functionality.
- The analysis says native call-graph targets remain uninspected, so it does not establish whether reporting runs by default or what data it sends.
Evidence against
- The package describes itself as a CLI for the TeamMesh service and routes `tm` to a bundled platform binary.
- The postinstall hook stages the binary and runs it with `--version` and an upgrade-notice command; the JavaScript hook contains no network request.
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 = 9462784
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-bV7Vg1/5-54e94b47e2da.txt
MediumAi Review Evidence.lpm-inspection-bV7Vg1/5-54e94b47e2da.txt
LowScripts Present
LowFilesystem
LowNo License
Affected versions and remediation
This report applies to teammesh@0.34.7.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.34.7 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.