teammesh@0.35.1
TeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe available native-binary strings indicate Sentry reporting and a crash-report toggle, but do not reveal the event payload or send conditions. The visible postinstall behavior is limited to validating and swapping in the package’s own binary.
Static reason
One or more suspicious static signals were detected.
Trigger
Potentially when the native CLI encounters a crash or reportable error; exact send conditions are not readable in the available binary analysis.
Impact
Diagnostic data may be sent to Sentry without clear disclosure in the inspected package files; no evidence shows credential collection.
Mechanism
The native binary contains Sentry transport code, a Sentry ingest endpoint, and a `TM_CRASH_REPORTS` toggle. The report contents and whether reporting is enabled by default could not be confirmed.
AI rationale
The available native-binary strings indicate Sentry reporting and a crash-report toggle, but do not reveal the event payload or send conditions. The visible postinstall behavior is limited to validating and swapping in the package’s own binary.
Evidence
.lpm-inspection-T07Vfi/5-3a46f32fffcb.txtinstall.jsbin/tm.jsbin/tm.js.native
Network endpoints3
o4512288884326400.ingest.us.sentry.ioapi.teammesh.iosync.teammesh.io
Decision evidence
public snapshotAI called this Suspicious at 77.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The native binary analysis shows Sentry transport code and a Sentry endpoint alongside a `TM_CRASH_REPORTS` toggle, indicating likely crash reporting; the report payload and send conditions are not readable.
- The postinstall hook runs only for npm on non-Windows platforms, stages the matching packaged binary, checks it with `--version`, and replaces the package’s `bin/tm.js` shim.
- The CLI shim runs the packaged platform binary with the user's supplied arguments.
Evidence against
- The install hook’s visible file operations stay within the package directory, and its executable check targets the package’s own native binary.
- The native analysis lists TeamMesh API and sync hosts, consistent with the package description as a team-connected CLI.
- No inspected source shows credentials being collected or sent to an unrelated host.
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"
},
"fi
Medium
Suspicious Lifecycle Evidence
The postinstall hook runs only for npm on non-Windows platforms, stages the matching packaged binary, checks it with `--version`, and replaces the package’s `bin/tm.js` shim.
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
MediumAi Review Evidence.lpm-inspection-T07Vfi/5-3a46f32fffcb.txt
MediumAi Review Evidence.lpm-inspection-T07Vfi/5-3a46f32fffcb.txt
MediumSuspicious Lifecycle Evidencepackage.json
MediumSuspicious Lifecycle Evidenceinstall.js
LowScripts Present
LowFilesystem
LowNo License
Affected versions and remediation
This report applies to teammesh@0.35.1.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.35.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.