@polymorphism-tech/morph-spec@9.5.0
MORPH-SPEC: NLH (Natural Language Harness) for spec-driven development with Claude Code
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package automatically configures a first-party statusline in global Claude settings, so a lifecycle-related agent extension warning is warranted. The inspected evidence does not establish malicious behavior, while an unresolved executable helper prevents a clean assurance.
Decision evidence
public snapshot- The package's postinstall launches global-install.js, which calls the global statusline installer automatically.
- That installer copies package scripts into the user's Claude directory and merges a command into global Claude settings; on Windows, selecting that command may attempt to install Python if it is missing.
- A Claude telemetry hook imports the shared e2e helper, whose offline analysis identifies it as an unrecognized executable artifact and leaves its behavior unresolved.
- The other inspected agent-integration locations concern a plugin check, project-local settings and MCP bookkeeping, worktree operations, or an explicit plugin command.
- The statusline reads Claude-provided JSON and derives the workspace directory for display.
- The plugin installer is exposed as a CLI command that requires a plugin name.
Source & flagged code
20 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage source references dynamic require/import behavior.
bin/morph-spec.jsView on unpkg · L10Findings
Affected versions and remediation
This report applies to @polymorphism-tech/morph-spec@9.5.0.
See all versions of @polymorphism-tech/morph-spec for other recorded verdicts.
- Review the evidence and your use of @polymorphism-tech/morph-spec@9.5.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.