pharaoh
v0.3.5Codebase knowledge graph with 23 development workflow skills. Query architecture, dependencies, blast radius, dead code, and test coverage via MCP. Requires...
⭐ 1· 99·0 current·0 all-time
byDan Greer@0xuxdesign
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
The name/description (codebase knowledge graph, MCP-based skills) align with required binaries (npx, node), the config path (~/.pharaoh/credentials.json), and network endpoints (mcp.pharaoh.so, github.com). Nothing requested appears unrelated to the stated purpose.
Instruction Scope
SKILL.md instructs running npx to install @pharaoh-so/mcp which copies SKILL.md skill files into ~/.openclaw/skills, adds an MCP entry to ~/.openclaw/openclaw.json, and then uses a local stdio proxy to relay requests to mcp.pharaoh.so where repositories are cloned and parsed server-side. This is coherent but does mean repository metadata and temporary clones are sent to an external service — a privacy/trust decision rather than a protocol mismatch.
Install Mechanism
No registry install spec is present; runtime install uses npx to pull an npm package. Fetching and running an external npm package is expected here but is higher risk than an instruction-only skill because arbitrary code is downloaded/executed at install/runtime. The SKILL.md points to a GitHub repo and npm package which should be audited before running.
Credentials
No unexpected environment variables or unrelated credentials are requested. The single config path (~/.pharaoh/credentials.json) is consistent with OAuth device flow and storing tokens. Note: the skill needs write access to ~/.openclaw/ and ~/.pharaoh/, which may contain other tooling config; adding an MCP entry to openclaw.json is part of its function.
Persistence & Privilege
The skill is not always-enabled and does not install background services. It writes its own credentials file and an MCP server entry in the OpenClaw config, which is normal for this functionality and does not indicate elevated system privileges.
Assessment
This skill appears to do what it says: it installs an npm MCP client, adds its skills to your OpenClaw skills folder, and relays repository metadata to Pharaoh's remote MCP server for parsing. Before installing: 1) Review the @pharaoh-so/mcp npm package source (GitHub and npm) to ensure you trust the code being fetched by npx. 2) Confirm your organization is comfortable installing the Pharaoh GitHub App (read-only contents and webhooks) and that its read-only scope meets policy. 3) If your repos contain sensitive information, consider using Pharaoh's self-hosted option or restrict installations to non-sensitive repositories — the service clones repos server-side and sends structural metadata to mcp.pharaoh.so. 4) Note tokens will be stored at ~/.pharaoh/credentials.json (owner-only permissions) and the installer will modify ~/.openclaw/openclaw.json and overwrite existing pharaoh skill files under ~/.openclaw/skills. 5) If you need higher assurance, ask for an install spec or publishable checksum for the npm package so you can validate the exact code that will run. If you want, I can list the specific things to audit in the GitHub repo and npm package before you run npx.Like a lobster shell, security has layers — review code before you run it.
latestvk9751aawp9swzxa8c286tpn6yh83mjfc
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binsnpx, node
Config~/.pharaoh/credentials.json