analyzthis_design@2.5.2
8 AI design personas — v2.5.2 motion/UX/visual library catalog and Kavi install detection, v2.5.1 anti-AI-slop craftsmanship, v2.5.0 signed rate-based persona trust scoring, v2.2 project-scoped knowledge bank, v2.0 chunked execution with frontier planner
AI Security Review
scanned 13d ago · by lpm-firewall-aiSource inspection found agent skill and MCP configuration changes only in the explicit CLI installer; the npm postinstall hook merely prints a message. This is a guarded, user-invoked agent integration capability, so warn rather than block.
Decision evidence
public snapshot- The install command copies package skills into project and user AI-tool directories, and the install path configures an MCP server for supported hosts.
- CLI install is activated by an explicit install command or by running the CLI without a command; package postinstall only prints guidance.
- The MCP setup adds an analyzthis_design server entry that runs npx analyzthis_design mcp.
- The cited knowledge and source-discovery locations describe project skill destinations and documentation scanning; they do not establish an independent control-surface attack.
- The package postinstall hook only prints a message; it does not invoke the installer.
- MCP configuration mutation is reached through the user-invoked CLI installer, not the npm lifecycle hook.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to analyzthis_design@2.5.2.
See all versions of analyzthis_design for other recorded verdicts.
- Review the evidence and your use of analyzthis_design@2.5.2 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.