teammesh@0.34.3
TeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe install hook visibly updates only the package’s CLI shim, but the opaque native CLI contains Sentry transport and ingest endpoint strings alongside a crash-report setting. Since the reporting behavior and disclosure cannot be confirmed from the available analysis, warn for possible undisclosed runtime telemetry.
Static reason
One or more suspicious static signals were detected.
Trigger
Potentially during CLI runtime when crash reporting is activated; exact trigger is unresolved.
Impact
Possible runtime crash telemetry sent to Sentry; no evidence establishes that credentials or other sensitive data are collected.
Mechanism
The native binary includes Sentry transport strings, an ingest endpoint, and a TM_CRASH_REPORTS setting. Its reporting logic and payload are not readable in the available analysis.
AI rationale
The install hook visibly updates only the package’s CLI shim, but the opaque native CLI contains Sentry transport and ingest endpoint strings alongside a crash-report setting. Since the reporting behavior and disclosure cannot be confirmed from the available analysis, warn for possible undisclosed runtime telemetry.
Evidence
.lpm-inspection-xRmSal/5-aa6ab650667e.txtinstall.jspackage.jsonbin/tm.js
Network endpoints1
o4512288884326400.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Suspicious at 78.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest declares a postinstall hook and routes the tm command through bin/tm.js.
- The install hook conditionally stages the bundled native binary, checks it with --version, and replaces the local shim.
- The native binary analysis identifies the Sentry crate and a SendEnvelope task.
- The binary analysis contains a Sentry ingest URL and the TM_CRASH_REPORTS setting; it does not establish the reporting trigger, payload, or whether reporting is enabled by default.
Evidence against
- The install hook’s visible behavior is limited to replacing the package’s own CLI shim and checking the bundled binary; it contains no visible network request.
- The native binary is the package’s CLI, described as connecting AI coding agents to a team, and the available analysis does not show credential collection or an unrelated collector.
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 unpkg14"bin": {
"tm": "bin/tm.js"
},
"scripts": {
"postinstall": "node install.js"
},
"files": [
"bin",
"native",
"install.js",
Medium
Suspicious Lifecycle Evidence
The manifest declares a postinstall hook and routes the tm command through bin/tm.js.
package.jsonView on unpkg · L14native/win32-arm64/tm.exeView file
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
MediumSuspicious Lifecycle Evidencepackage.json
MediumSuspicious Lifecycle Evidenceinstall.js
MediumAi Review Evidence.lpm-inspection-xRmSal/5-aa6ab650667e.txt
MediumAi Review Evidence.lpm-inspection-xRmSal/5-aa6ab650667e.txt
LowScripts Present
LowFilesystem
LowNo License
Affected versions and remediation
This report applies to teammesh@0.34.3.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.34.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.