@mulmoclaude/core@4.9.4
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 package provides an explicit registry-import feature that mirrors allowlisted files into Claude’s skill directory. This is a warning-level agent capability; the inspected source does not show install-time mutation or a concrete attack.
Decision evidence
public snapshot- package.json defines build, typecheck, test, and lint scripts, with no install lifecycle hook.
- Registry imports can mirror skill files into the workspace’s `.claude/skills` directory.
- The bridge limits mirrored files to `SKILL.md`, `schema.json`, and safe action-template paths.
- An explicit `importRegistry` call runs the import operation that reaches the mirror step.
- The mirror runs as part of a registry import operation, not an npm lifecycle hook.
- The bridge rejects paths outside the staging tree and checks skill slugs and allowed paths.
Source & flagged code
4 flagged · loading sourcePackage metadata claims a different repository identity while copied source loads a runtime dependency bridge.
dist/discovery-BkIKvdh0.jsView on unpkg · L1448Findings
Affected versions and remediation
This report applies to @mulmoclaude/core@4.9.4.
See all versions of @mulmoclaude/core for other recorded verdicts.
- Review the evidence and your use of @mulmoclaude/core@4.9.4 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.