teammesh@0.30.3
TeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe binary’s strings indicate possible Sentry crash reporting, while the available analysis cannot establish its default behavior, data contents, or disclosure. The readable install hook only probes and installs a bundled local binary, so the evidence supports a telemetry warning rather than a malicious verdict.
Static reason
One or more suspicious static signals were detected.
Trigger
Potentially when the native CLI runs or encounters a crash; the available static analysis does not establish the exact trigger or default setting.
Impact
If enabled by default without disclosure, crash reports could send runtime information to Sentry; the contents could not be determined from the available evidence.
Mechanism
The extracted binary strings include a Sentry DSN and a `TM_CRASH_REPORTS` environment-variable name, but the relevant native call paths were not fully analyzed.
AI rationale
The binary’s strings indicate possible Sentry crash reporting, while the available analysis cannot establish its default behavior, data contents, or disclosure. The readable install hook only probes and installs a bundled local binary, so the evidence supports a telemetry warning rather than a malicious verdict.
Evidence
native/win32-x64/tm.exe.lpm-inspection-EOOZ89/5-fc42de07d24d.txtinstall.jsbin/tm.js
Network endpoints3
api.teammesh.iosync.teammesh.ioo4512288884326400.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Suspicious at 68.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The Windows binary’s extracted strings contain a Sentry crash-report endpoint and a `TM_CRASH_REPORTS` environment-variable name.
- The available binary analysis says some call targets were not inspected, so it does not establish whether reporting is enabled by default, what it sends, or how users are informed.
- The readable postinstall script probes the staged local binary with `--version` before replacing the CLI shim; its visible behavior shows no install-time network request.
- The binary also contains TeamMesh API and sync URLs, which are consistent with the package’s stated purpose.
Evidence against
- The install hook is limited to npm on non-Windows platforms and uses a bundled binary.
- The available static evidence does not confirm that the Sentry endpoint is contacted or that crash reports include sensitive data.
Behavioral surface
ChildProcessEnvironmentVarsFilesystem
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 = 9337856
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-EOOZ89/5-fc42de07d24d.txt
MediumAi Review Evidence.lpm-inspection-EOOZ89/5-fc42de07d24d.txt
MediumSuspicious Lifecycle Evidenceinstall.js
MediumSuspicious Lifecycle Evidenceinstall.js
LowScripts Present
LowFilesystem
LowNo License
Affected versions and remediation
This report applies to teammesh@0.30.3.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.30.3 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.