@polymorphism-tech/morph-spec@9.2.0
⚠ Under reviewMORPH-SPEC: NLH (Natural Language Harness) for spec-driven development with Claude Code
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe inspected readable code shows package setup behavior but does not establish malicious activity. A required executable hook remains materially unresolved, so manual review is appropriate.
Decision evidence
public snapshot- package.json runs a postinstall script that invokes the global installer.
- The global installer sets up a status line in Claude’s global configuration.
- The required executable hook artifact has no supported analysis, leaving its behavior unresolved.
- The inspected plugin command requires a plugin name and invokes installation through an explicit CLI command.
- The inspected MCP installer code identifies existing plugin-provided servers to avoid starting them twice.
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.2.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.2.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.