@papi-ai/server@0.7.75
PAPI MCP server — AI-powered sprint planning, build execution, and strategy review for software projects
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe scanner's command-exfiltration claim is not supported by the inspected source: child-process use is project Git/GitHub workflow functionality. The confirmed concern is explicit setup-time Claude configuration and a project hook, which warrants a warning rather than a block.
Decision evidence
public snapshot- dist/index.js: explicit setup writes .claude/settings.json
- dist/index.js: setup installs a PreToolUse shell hook for Edit/Write
- design-assets/hooks/frontend-design-guard.sh: hook reads tool input and emits warnings
- dist/index.js: runtime telemetry posts tool metadata to PAPI Supabase
- package.json has no preinstall/install/postinstall hook
- setup is an explicitly invoked MCP tool with prepare/apply flow
- hook is scoped to active PAPI UI edits and exits without blocking
- telemetry is documented and can be disabled with PAPI_TELEMETRY=off
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 · L4307Findings
Affected versions and remediation
This report applies to @papi-ai/server@0.7.75.
See all versions of @papi-ai/server for other recorded verdicts.
- Review the evidence and your use of @papi-ai/server@0.7.75 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.