@papi-ai/server@0.7.98
PAPI MCP server — AI-powered sprint planning, build execution, and strategy review for software projects
AI Security Review
scanned 19d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and inspected agent configuration changes are associated with explicit commands or project setup. Credential and network behavior inspected is tied to PAPI settings or operator-provided endpoint configuration, with no confirmed attack behavior.
Decision evidence
public snapshot- package.json points to the server entrypoint and lists build, start, backfill, and prepack scripts; it has no install lifecycle hook.
- The backfill match selects Claude instruction files and documentation for a Git diff; it does not write agent configuration.
- The index match likewise selects Claude instruction files and documentation for a Git diff.
- The statusline reads PAPI server settings from the project’s MCP configuration; its settings write is gated by an explicit install option.
- The server adds its project design hook during local project setup when a frontend stack is detected.
- Prompt retrieval uses operator-provided endpoint and API-key environment variables; telemetry is gated and uses PAPI data credentials.
Source & flagged code
6 flaggedPackage source references child process execution.
dist/backfill-cycle-metrics.jsView on unpkg · L261Manifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
dist/index.jsFindings
Affected versions and remediation
This report applies to @papi-ai/server@0.7.98.
See all versions of @papi-ai/server for other recorded verdicts.
- Review the evidence and your use of @papi-ai/server@0.7.98 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.