@mulmoclaude/core@5.5.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-aiSource inspection found a first-party capability that installs or updates skill files in the active Claude skills directory during runtime collection operations. With no npm lifecycle hook or evidence of covert or broad control-surface mutation, this warrants a warning rather than a block.
Decision evidence
public snapshot- The manifest lists build, typecheck, test, and lint scripts, with no npm install lifecycle hook in the scripts section.
- The skill bridge maps allowlisted skill files from workspace staging into the active .claude/skills tree; its targets are slug-scoped.
- Registry import selects the project skill directory and tracks whether files need mirroring.
- A server operation writes a validated schema and mirrors it into the active skill tree.
- The flagged server bundles contain project collection rendering and validation logic; the discovery bundle loads package-local modules, and the prompt safety and Google bundles contain package functionality.
- The bridge is runtime functionality rather than an npm lifecycle hook.
- The inspected sources do not show credential collection or an unrelated data recipient.
- The bridge targets skill files and uses an atomic write; no broad agent configuration mutation was identified.
Source & flagged code
4 flagged · loading sourcePackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/discovery-B79IxEM6.cjsView on unpkg · L1450Findings
Affected versions and remediation
This report applies to @mulmoclaude/core@5.5.1.
See all versions of @mulmoclaude/core for other recorded verdicts.
- Review the evidence and your use of @mulmoclaude/core@5.5.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.