@mulmoclaude/core@5.5.0
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 flagged agent configuration behavior is scoped to the package’s collection skill authoring and import workflow, with workspace path and file allowlisting. Inspected evidence did not establish install-hook activation, broad unrelated agent configuration changes, credential exposure, or another concrete attack.
Decision evidence
public snapshot- package.json identifies this as a shared MulmoClaude and MulmoTerminal core package.
- The registry import behavior installs skills under the active .claude/skills directory when no staging bridge exists; with staging, skill files are mirrored into that directory.
- The skill bridge limits mirrored paths to validated skill slugs and allowed files under the workspace staging directory.
- Schema mirroring is tied to a schema write operation in the collection server, consistent with package-owned collection authoring.
- The flagged server bundle excerpts describe source-aware collection view handling; the flagged discovery, prompt safety, and Google files inspected begin with ordinary module imports.
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.0.
See all versions of @mulmoclaude/core for other recorded verdicts.
- Review the evidence and your use of @mulmoclaude/core@5.5.0 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.