teammesh@0.35.2
TeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe install hook runs native code automatically, and the available binary analysis shows a Sentry endpoint with a crash-reporting flag but cannot establish its behavior or consent controls. This is an unresolved telemetry concern, not evidence of credential theft or other malicious activity.
Static reason
One or more suspicious static signals were detected.
Trigger
The npm postinstall hook runs the native binary for a version check and an upgrade notice; later CLI use may also initialize reporting.
Impact
If reporting runs without disclosure or an effective opt-out, runtime error details may be sent to Sentry.
Mechanism
A bundled binary contains a Sentry ingest endpoint and the string TM_CRASH_REPORTS, but the analysis does not reveal whether reporting is enabled by default or what data is sent.
AI rationale
The install hook runs native code automatically, and the available binary analysis shows a Sentry endpoint with a crash-reporting flag but cannot establish its behavior or consent controls. This is an unresolved telemetry concern, not evidence of credential theft or other malicious activity.
Evidence
install.jsnative/win32-x64/tm.exebin/tm.jsbin/tm.js.native
Network endpoints1
o4512288884326400.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Suspicious at 73.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The postinstall hook runs the bundled native CLI with --version and then invokes __pools-upgrade-notice.
- The bundled Windows x64 binary analysis contains a Sentry ingest URL adjacent to TM_CRASH_REPORTS; the available analysis does not establish when reports are sent or what they contain.
Evidence against
- The manifest describes TeamMesh as a CLI for connecting AI coding agents to a team.
- The install hook stages a platform-matched bundled binary and skips replacement if it cannot run.
Behavioral surface
ChildProcessEnvironmentVarsFilesystem
NoLicense
Source & flagged code
6 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 = 9463296
magicHex = [redacted]
Medium
Findings
1 High7 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
MediumSuspicious Lifecycle Evidenceinstall.js
MediumSuspicious Lifecycle Evidenceinstall.js
MediumAi Review Evidence.lpm-inspection-PapV7q/5-d387efc7aa6e.txt
LowScripts Present
LowFilesystem
LowNo License
Affected versions and remediation
This report applies to teammesh@0.35.2.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.35.2 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.