teammesh
TeamMesh CLI: connects AI coding agents to your team
This report shows the evidence for teammesh@0.49.1. 0 of 70 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 2h ago · by lpm-firewall-aiThe install hook and launcher behave consistently with installing and running the package’s native CLI. However, the limited binary analysis reveals Sentry crash-reporting components without establishing consent, defaults, or collected data, so runtime telemetry remains a user-relevant uncertainty.
Static reason
One or more suspicious static signals were detected.
Trigger
The postinstall hook runs during npm installation; the binary otherwise runs when the user invokes tm.
Impact
Undisclosed runtime crash telemetry may disclose diagnostic information; the available evidence does not show credential theft or unrelated data collection.
Mechanism
The install hook checks the native binary with --version and may request an upgrade notice. A limited analysis view shows a Sentry endpoint and TM_CRASH_REPORTS setting, but not their runtime behavior.
AI rationale
The install hook and launcher behave consistently with installing and running the package’s native CLI. However, the limited binary analysis reveals Sentry crash-reporting components without establishing consent, defaults, or collected data, so runtime telemetry remains a user-relevant uncertainty.
Evidence
.lpm-inspection-ijG8Qf/5-1018b23127e6.txtinstall.jsbin/tm.jsbin/tm.js.nativenative/<platform>-<arch>/tm
Network endpoints3
api.teammesh.iosync.teammesh.io39a18618b3abf2d4bee26b2b5fefc1d6@o4512288884326400.ingest.us.sentry.io/4512288887013376
Decision evidence
public snapshotAI called this Suspicious at 72.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest runs install.js as a postinstall hook.
- On supported npm installs, the hook copies a native binary, marks it executable, runs it with --version, and may invoke an upgrade-notice command.
- The native analysis view contains a Sentry crash-reporting endpoint and the TM_CRASH_REPORTS setting, but does not establish whether reporting is enabled by default or what data it sends.
- The binary also contains TeamMesh API and sync endpoints consistent with the CLI’s stated purpose.
- The available native analysis is limited and leaves parts of the binary behavior uninspected.
Evidence against
- The install hook limits binary replacement to supported platforms and npm, and falls back without failing if the check does not work.
- The launcher selects the binary matching the current platform and forwards the user’s command-line arguments.
- The observed API and sync endpoints belong to the package’s own service.
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 unpkg18"postinstall": "node install.js"
},
"files": [
"bin",
"native",
"install.js",
"LICENSE"
],
"engines": {
"node": ">=18"
}
}
Medium
Suspicious Lifecycle Evidence
The manifest runs install.js as a postinstall hook.
package.jsonView on unpkg · L18native/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
MediumAi Review Evidenceinstall.js
MediumAi Review Evidence.lpm-inspection-ijG8Qf/5-1018b23127e6.txt
MediumAi Review Evidence.lpm-inspection-ijG8Qf/5-1018b23127e6.txt
LowScripts Present
LowFilesystem
LowNo License
Affected versions and remediation
This report applies to teammesh@0.49.1.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of teammesh@0.49.1 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.