@mulmoclaude/core@5.3.0
Shared server-side core for MulmoClaude and MulmoTerminal — the always-shipped-together subsystems consolidated behind subpath exports so the two hosts can't drift. Server-only except the browser-safe ./artifacts, ./whisper/client, ./workspace-setup/slug,
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe source establishes a user-invoked registry import that adds allowlisted skill files to a project Claude skills directory. With no npm lifecycle trigger, this fits the warning category for agent extension setup rather than a malicious install hook.
Decision evidence
public snapshot- An explicit registry import can mirror imported skill files into the project’s `.claude/skills` directory.
- The mirror copies only `SKILL.md`, `schema.json`, and paths accepted by the action-template allowlist.
- The package manifest lists build, typecheck, test, and lint scripts; no install lifecycle hook is present.
- The observed mirror is conditional on a registry import and a project staging directory; the manifest shows no npm install hook that triggers it.
Source & flagged code
4 flagged · loading sourcePackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/discovery-B_64PBZU.jsView on unpkg · L1448Findings
Affected versions and remediation
This report applies to @mulmoclaude/core@5.3.0.
See all versions of @mulmoclaude/core for other recorded verdicts.
- Review the evidence and your use of @mulmoclaude/core@5.3.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.