teammesh@0.34.13
TeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe native binary embeds a Sentry ingest endpoint next to a crash-reporting setting, suggesting runtime telemetry whose default and payload cannot be established from the available static view. The postinstall script's shim replacement and upgrade notice are consistent with the CLI's stated purpose.
Static reason
One or more suspicious static signals were detected.
Trigger
Potentially when the native CLI reports a crash; the static artifact does not establish whether reporting is enabled by default.
Impact
If enabled, crash reports may disclose runtime details to Sentry without clear disclosure in the inspected package source.
Mechanism
The native binary contains a Sentry ingest URL and the TM_CRASH_REPORTS setting. The available static view does not reveal the transmitted fields or confirm the setting's behavior.
AI rationale
The native binary embeds a Sentry ingest endpoint next to a crash-reporting setting, suggesting runtime telemetry whose default and payload cannot be established from the available static view. The postinstall script's shim replacement and upgrade notice are consistent with the CLI's stated purpose.
Evidence
native/win32-x64/tm.exe.lpm-inspection-I3pdwe/5-7e9e371c8dfa.txtbin/tm.js
Network endpoints1
39a18618b3abf2d4bee26b2b5fefc1d6@o4512288884326400.ingest.us.sentry.io/4512288887013376
Decision evidence
public snapshotAI called this Suspicious at 73.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The Windows x64 native binary contains a Sentry ingest URL adjacent to the TM_CRASH_REPORTS setting, indicating possible crash reporting; the available static view does not establish its default or payload.
- The native binary also contains the package's own API and sync endpoints, consistent with the stated CLI purpose.
Evidence against
- The package describes itself as a CLI that connects AI coding agents to a team and exposes it through the tm command.
- The postinstall hook is limited to npm on non-Windows platforms, checks for a matching bundled binary, and uses it to replace the CLI shim.
- The hook's additional native invocation requests an upgrade notice for an existing pools manager; the source says ordinary installs stay silent.
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 = 9469952
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-I3pdwe/5-7e9e371c8dfa.txt
MediumAi Review Evidence.lpm-inspection-I3pdwe/5-7e9e371c8dfa.txt
LowScripts Present
LowFilesystem
LowNo License
Affected versions and remediation
This report applies to teammesh@0.34.13.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.34.13 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.