@papi-ai/server@0.7.76
PAPI MCP server — AI-powered sprint planning, build execution, and strategy review for software projects
AI Security Review
scanned 3mo ago · by lpm-firewall-aiSource inspection disproves the scanner's install-time and command-output-exfiltration implication. The remaining user-triggered agent configuration and default identifiable telemetry justify a warning, not a block.
Decision evidence
public snapshot- dist/index.js automatically reads git/GitHub email for md-mode user ID.
- dist/index.js sends md-mode telemetry with install ID, user ID, project slug, tool name, and result metadata.
- dist/index.js can write PAPI MCP entries to project and user-scoped agent configs through explicit setup/init actions.
- dist/index.js executes git/gh commands for its project-management tools.
- package.json has no preinstall, install, or postinstall hook.
- Config writes occur only through explicit CLI/MCP setup or init paths; reset prompts before removal.
- No remote payload download/eval chain or arbitrary shell execution was found.
- Observed endpoints are PAPI/Supabase service endpoints aligned with the package's hosted adapter.
Source & flagged code
8 flaggedPackage source references child process execution.
dist/backfill-cycle-metrics.jsView on unpkg · L81A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/backfill-cycle-metrics.jsView on unpkg · L4320Findings
Affected versions and remediation
This report applies to @papi-ai/server@0.7.76.
See all versions of @papi-ai/server for other recorded verdicts.
- Review the evidence and your use of @papi-ai/server@0.7.76 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.