@mutmutco/codex-plugin@4.5.133
MMI workflow skills and org gates delivery.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe CLI forwards a locally available GitHub credential to the package-selected MMI Hub during ordinary Hub authentication without recipient-specific consent. This is concrete credential exposure, so the package should be blocked.
Decision evidence
public snapshot- The cited agent-related code only filters untracked agent configuration and session paths in a Git cleanliness check; it does not write agent settings.
- The CLI reads GitHub credentials from environment variables or from the GitHub CLI token command.
- When a Hub session is not cached, the normal path sends the GitHub token as bearer authentication to the Hub session endpoint; an MMI Hub token can bypass that path but is not required to use it.
- The Hub recipient defaults to the package-selected MMI endpoint, and shared Hub headers obtain authentication using the GitHub token.
- A Hub-backed board operation uses those shared authenticated headers.
- The manifest contains no npm lifecycle scripts; the credential transfer occurs during CLI runtime.
- The package also sends limited command, version, operating-system, and CI telemetry to the Hub, with an environment-variable opt-out; that telemetry does not account for the GitHub credential transfer.
Source & flagged code
7 flagged · loading sourceSource appears to send environment or credential material to an external endpoint.
cli/dist/main.cjsView on unpkg · L39This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
cli/dist/main.cjsView on unpkgFindings
Affected versions and remediation
This report applies to @mutmutco/codex-plugin@4.5.133.
See all versions of @mutmutco/codex-plugin for other recorded verdicts.
- Avoid installing @mutmutco/codex-plugin@4.5.133. 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.