@mulmoclaude/core@5.0.1
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 confirms a constrained skill-file bridge, but no npm lifecycle hook or concrete malicious behavior. The flagged configuration writes are limited to registry skill import behavior, so the static signals do not establish an attack.
Decision evidence
public snapshot- The package exposes build and development scripts, with no preinstall, install, or postinstall hook in the inspected script block.
- Registry import code mirrors selected skill files into the workspace’s .claude/skills directory.
- The bridge limits mirrored files to SKILL.md, schema.json, and safe action templates.
- The bridge resolves files beneath data/skills and rejects paths outside that staging directory or outside its allowlist.
- No inspected source shows an npm lifecycle trigger or a concrete attack chain.
Source & flagged code
4 flagged · loading sourcePackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/discovery-CBjI1lx9.jsView on unpkg · L1448Findings
Affected versions and remediation
This report applies to @mulmoclaude/core@5.0.1.
See all versions of @mulmoclaude/core for other recorded verdicts.
- Review the evidence and your use of @mulmoclaude/core@5.0.1 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.