@mmerterden/multi-agent-pipeline@16.30.0
8-phase AI development pipeline with full orchestration on Claude Code, Copilot CLI and Codex CLI. Analysis, planning, TDD, CLI-aware parallel review with consensus surfacing + Fable triage, default-FAIL evidence gates, secret + intent guards, per-phase c
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package has no npm lifecycle hook, and its agent setup is reached through an explicit CLI install command. The inspected network telemetry is opt-in and sends package/runtime metadata, so the scanner hints do not establish malicious behavior.
Decision evidence
public snapshot- The manifest exposes a command-line entry point and defines no npm lifecycle hooks.
- The entry point loads the installer for an explicit install command; the installer dispatches to selected CLI installers that write into their corresponding home-directory configuration locations.
- The listed agent and memory scripts use host-specific configuration or repository-scoped storage paths for their product functions.
- Install telemetry returns unless the user sets an explicit environment opt-in; its request sends package and runtime metadata to the package's telemetry endpoint.
Source & flagged code
9 flagged · loading sourcePackage contains a possible secret pattern.
pipeline/scripts/keychain.pyView on unpkg · L143Hardcoded password in pipeline/scripts/keychain.py
pipeline/scripts/keychain.pyView on unpkg · L159Package source references child process execution.
pipeline/scripts/triage-memory.mjsFindings
Affected versions and remediation
This report applies to @mmerterden/multi-agent-pipeline@16.30.0.
See all versions of @mmerterden/multi-agent-pipeline for other recorded verdicts.
- Review the evidence and your use of @mmerterden/multi-agent-pipeline@16.30.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.