@papi-ai/server@0.7.126
PAPI MCP server — AI-powered sprint planning, build execution, and strategy review for software projects
AI Security Review
scanned 1mo ago · by lpm-firewall-aiSource supports a warning for explicit agent configuration mutation, rather than a malware block. Scanner credential and configuration labels do not establish covert theft or install-time control hijacking.
Decision evidence
public snapshot- package.json has no registry-install lifecycle hooks or runtime self-dependency.
- The MCP setup tool invokes project scaffolding that changes agent configuration.
- Setup allows all PAPI tools in Claude settings and registers an Edit/Write command hook.
- The status-line installer requires --install and configures a command that invokes @papi-ai/cli through npx.
- The flagged backfill location reads CLAUDE.md paths from Git history rather than changing agent instructions.
- No concrete malicious install behavior or covert credential theft was established.
- CLI authentication obtains a PAPI credential through browser-approved device authorization.
- The design hook checks for an active PAPI build and emits a warning without blocking edits.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/backfill-cycle-metrics.jsView on unpkg · L271Findings
Affected versions and remediation
This report applies to @papi-ai/server@0.7.126.
See all versions of @papi-ai/server for other recorded verdicts.
- Review the evidence and your use of @papi-ai/server@0.7.126 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.