@papi-ai/server@0.402.157
PAPI MCP server — AI-powered sprint planning, build execution, and strategy review for software projects
AI Security Review
scanned 20d ago · by lpm-firewall-aiSource inspection found no install lifecycle hook or concrete attack behavior. The flagged statusline write requires explicit installation, while setup, telemetry, and backfill behavior align with the package's stated server functions.
Decision evidence
public snapshot- The manifest has no install lifecycle hook; it declares ordinary build and runtime scripts.
- Setup contacts the PAPI service for a device code and stores the returned API key locally after approval.
- Telemetry sends tool and event metadata to the configured PAPI data endpoint only when enabled and configured.
- The statusline settings write requires an explicit install flag and leaves an existing status command untouched.
- The backfill command runs when directly invoked; its Git commands read user identity, and its runtime writes calculated cycle metrics.
- The flagged project-document paths are inputs to project file discovery, not instructions to the reviewer.
Source & flagged code
10 flaggedPackage source references child process execution.
dist/backfill-cycle-metrics.jsView on unpkg · L982A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/backfill-cycle-metrics.jsView on unpkg · L3763Findings
Affected versions and remediation
This report applies to @papi-ai/server@0.402.157.
See all versions of @papi-ai/server for other recorded verdicts.
- Review the evidence and your use of @papi-ai/server@0.402.157 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.