lm-assist
Full observability & control for the Claude product line — Claude Code (local/remote/cloud), claude.ai conversations, Cowork, agents, memory, connectors, usage — via web dashboard, REST API, and MCP tools
This report shows the evidence for lm-assist@0.2.4. 2 of 3 known versions are blocked or flagged. The newest version, 0.2.5, is flagged. See all versions.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe automatic postinstall chain mutates Claude Code's control surface and installs an external plugin during npm installation. This is concrete unconsented install-hook abuse.
Decision evidence
public snapshot- The manifest runs a postinstall script automatically.
- For global installs, postinstall starts the package services and requests statusline installation.
- Postinstall automatically adds a Claude marketplace and installs a Claude plugin when the CLI is present.
- The invoked statusline route writes a command into Claude Code settings.
- The postinstall script exits for source installs.
- No runtime dependency on lm-assist itself appears in the manifest.
Source & flagged code
34 flagged · loading sourceSource creates an unconsented AI-agent control surface through install-time mutation or a default unauthenticated remote skill channel.
package.jsonView on unpkg · L44Package defines install-time lifecycle scripts.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to lm-assist@0.2.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing lm-assist@0.2.4. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.