@mulmoclaude/core@5.6.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 shows a bounded, host-triggered setup that makes imported skills available to Claude, so it merits a warning under the agent integration policy. No concrete malicious behavior or npm install hook was established.
Decision evidence
public snapshot- The manifest has no install lifecycle hook; its scripts are build, typecheck, test, and lint.
- Registry imports mirror allowlisted skill files into the workspace’s active Claude skills directory.
- The skill bridge limits mirrored files to SKILL.md, schema.json, and safe action templates.
- The import function performs registry import when called by the host; this is an explicit integration path, not an npm install hook.
- The server bundles describe reading imported views from the Claude skills directory, consistent with the bridge’s package feature.
- The bridge does not copy arbitrary files: it checks workspace-relative paths, validates the skill slug, and applies an allowlist.
- The inspected source did not establish a concrete malicious payload, credential theft, or unconsented install-time mutation.
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.6.1.
See all versions of @mulmoclaude/core for other recorded verdicts.
- Review the evidence and your use of @mulmoclaude/core@5.6.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.