teammesh@0.32.0
TeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe postinstall hook only stages the package’s own binary, checks its version, and replaces the launcher. The native analysis exposes a Sentry endpoint and a crash-reporting setting, but does not resolve activation, payload, or disclosure, so this is suspicious runtime telemetry rather than a confirmed attack.
Static reason
One or more suspicious static signals were detected.
Trigger
Potentially when the native CLI runs and encounters a reportable event; the available analysis does not establish the trigger or setting behavior.
Impact
Runtime diagnostics or stack traces may be sent to Sentry without clear disclosure or consent.
Mechanism
The binary embeds a Sentry ingestion URL and the TM_CRASH_REPORTS setting; the report contents and consent controls could not be confirmed.
AI rationale
The postinstall hook only stages the package’s own binary, checks its version, and replaces the launcher. The native analysis exposes a Sentry endpoint and a crash-reporting setting, but does not resolve activation, payload, or disclosure, so this is suspicious runtime telemetry rather than a confirmed attack.
Evidence
.lpm-inspection-3CcENm/5-0a53bf391236.txtinstall.jsbin/tm.js
Network endpoints1
o4512288884326400.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Suspicious at 76.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The Windows binary’s embedded strings contain a Sentry ingestion URL adjacent to the TM_CRASH_REPORTS setting.
- The available native analysis says its call graph is incomplete, so it does not establish whether reporting is enabled by default or what data is sent.
- The postinstall hook runs the bundled binary with --version before replacing the JavaScript shim.
Evidence against
- The postinstall hook is limited to staging a bundled platform binary and replacing bin/tm.js; no network request appears in the inspected hook.
- The package’s JavaScript launcher forwards arguments to the bundled native CLI.
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 = 9424384
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
MediumAi Review Evidence.lpm-inspection-3CcENm/5-0a53bf391236.txt
MediumAi Review Evidence.lpm-inspection-3CcENm/5-0a53bf391236.txt
MediumSuspicious Lifecycle Evidenceinstall.js
LowScripts Present
LowFilesystem
LowNo License
Affected versions and remediation
This report applies to teammesh@0.32.0.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.32.0 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.