@mulmoclaude/core@5.11.2
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 registry import path can write behavior-bearing skill files into Claude’s active workspace skills directory, so this is a guarded agent capability. No evidence shows that npm installation triggers it or that the behavior is malicious; classify as suspicious and warn.
Decision evidence
public snapshot- package.json defines build, typecheck, test, and lint scripts, with no install lifecycle hook.
- Registry import validates a bundle, writes it to the selected skill directory, and mirrors allowed files into `.claude/skills/<slug>`.
- The skill bridge copies staged skill files into Claude’s active skills directory; this is a real agent configuration capability.
- Google broker credentials use a package-associated HTTPS endpoint by default; HTTP overrides are restricted to loopback.
- The skill bridge restricts mirrored paths to safe skill files and templates, and validates slugs and staging paths.
- The agent configuration writes occur in registry import or staging flows, not through an npm lifecycle hook.
- No concrete credential theft, destructive behavior, or remote code execution 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-CbwHtcwk.jsView on unpkg · L1447Findings
Affected versions and remediation
This report applies to @mulmoclaude/core@5.11.2.
See all versions of @mulmoclaude/core for other recorded verdicts.
- Review the evidence and your use of @mulmoclaude/core@5.11.2 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.