@papi-ai/server@0.402.35
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 and persistent execution capability. The absence of registry-install hooks and the explicit activation gates do not support blocking this release as malicious.
Decision evidence
public snapshot- package.json has no preinstall, install, or postinstall hook and no runtime self-dependency.
- The flagged location in dist/backfill-cycle-metrics.js queries Git history for documentation paths rather than modifying agent configuration.
- The explicit setup tool in dist/index.js adds wildcard PAPI tool permissions to project Claude settings and can register a frontend design hook.
- The statusline helper writes a command invoking npx into user Claude settings only when explicitly invoked with --install; existing statusline entries are preserved.
- No confirmed credential theft, hidden payload execution, or malicious install-time mutation was established.
- Statusline authentication uses caller-supplied credentials or the bearer configured for the same MCP endpoint.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/backfill-cycle-metrics.jsView on unpkg · L863Findings
Affected versions and remediation
This report applies to @papi-ai/server@0.402.35.
See all versions of @papi-ai/server for other recorded verdicts.
- Review the evidence and your use of @papi-ai/server@0.402.35 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.