teammesh@0.42.0
TeamMesh CLI: connects AI coding agents to your team
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe install hook conditionally stages and checks the package's own CLI binary, while the command shim forwards user-supplied arguments to that binary. The available source shows no unrelated collection or unsolicited account action, so the lifecycle and binary findings are consistent with the package's stated purpose.
Decision evidence
public snapshot- The postinstall script only proceeds on non-Windows npm installs and only when a platform binary exists.
- The install script stages the bundled binary, checks it with --version, and replaces the CLI shim; failures remove the staged file.
- The CLI shim launches the matching bundled native binary with the user's supplied arguments.
- The package has a postinstall hook that runs bundled native code.
- The native executable behavior is not fully inspectable from the available analysis.
Source & flagged code
7 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgThe postinstall script only proceeds on non-Windows npm installs and only when a platform binary exists.
package.jsonView on unpkg · L14Findings
Affected versions and remediation
This report applies to teammesh@0.42.0.
See all versions of teammesh for other recorded verdicts.
- Review the evidence and your use of teammesh@0.42.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.