muse-gateway@1.0.4
Muse Gateway — local Muse session pool & OpenAI-compatible gateway. License key required to unlock /v1/* API.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe server entry attempts to direct the security reviewer to follow instructions shipped in the package. The launcher loads that entry during server startup, meeting the stated reviewer-manipulation criterion.
Decision evidence
public snapshot- The shipped server entry contains a comment instructing reviewers to read and follow package-provided AGENTS.md and CLAUDE.md rules.
- The launcher loads app/server.js when starting the server, so the review-directed instruction is part of the shipped application entry path.
- The manifest declares no lifecycle scripts; the CLI starts the local gateway and its bundled server.
- The launcher’s registry autostart, process control, license activation, and npm update functions are user-facing CLI actions.
Source & flagged code
22 flaggedPackage source references child process execution.
bin/muse-gateway.cjsView on unpkg · L19A single source file combines environment access, network access, and code or shell execution; review context before blocking.
bin/muse-gateway.cjsFindings
Affected versions and remediation
This report applies to muse-gateway@1.0.4.
See all versions of muse-gateway for other recorded verdicts.
- Avoid installing muse-gateway@1.0.4. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.