SkillAudit report — posthog/mcp
Scanned 2026-04-24 by SkillAudit v0.2 (static checks + LLM-assisted prompt-injection red-team).
Commit: 13aaf2c · Stars: 143 · Days since last push: 94
LLM prompt-injection probe: no-tool-surface
Overall grade: F (0/100)
| Axis | Score | Grade | |
|---|---|---|---|
| security | 10/100 | F | ❌ |
| permissions | 100/100 | A | ✅ |
| credentials | 0/100 | F | ❌ |
| maintenance | 70/100 | C | ⚠️ |
| compatibility | 70/100 | C | ⚠️ |
| docs | 70/100 | C | ⚠️ |
Security findings
Production sources:
- HIGH
typescript/scripts/update-openapi-client.ts:14— HTTP client call with user-controlled argument 'SCHEMA_URL' — no URL allowlist / validation found in file
const response = await fetch(SCHEMA_URL);
- HIGH
typescript/scripts/update-openapi-client.ts:34— child_process.exec with template-string interpolation — argv is concat-built, not escaped
execSync(\pnpm typed-openapi ${TEMP_SCHEMA_PATH} --output ${OUTPUT_PATH}\, {
- HIGH
typescript/src/api/client.ts:118— HTTP client call with user-controlled argument 'url' — no URL allowlist / validation found in file
const response = await fetch(url, {
- HIGH
typescript/src/api/client.ts:592— Template-string URL with interpolation — no validation possible on composed string
const deleteResponse = await fetch(
- HIGH
typescript/src/api/client.ts:762— Template-string URL with interpolation — no validation possible on composed string
const response = await fetch(
- HIGH
typescript/src/api/client.ts:889— Template-string URL with interpolation — no validation possible on composed string
const response = await fetch(
- HIGH
typescript/src/api/client.ts:1062— Template-string URL with interpolation — no validation possible on composed string
const response = await fetch(
- HIGH
typescript/src/api/client.ts:1228— Template-string URL with interpolation — no validation possible on composed string
const response = await fetch(
- HIGH
typescript/src/api/fetcher.ts:35— HTTP client call with user-controlled argument 'input' — no URL allowlist / validation found in file
const response = await fetch(input.url, {
- HIGH
typescript/src/lib/utils/api.ts:10— HTTP client call with user-controlled argument 'url' — no URL allowlist / validation found in file
const response = await fetch(url, {
Permissions
_No findings on this axis._
Credentials
Production sources:
- HIGH
examples/ai-sdk/.env.example:3— Hardcoded OpenAI / Anthropic-style API key found in source
sk-*** (OpenAI / Anthropic-style API key, 23 chars)
- HIGH
examples/langchain-js/.env.example:3— Hardcoded OpenAI / Anthropic-style API key found in source
sk-*** (OpenAI / Anthropic-style API key, 23 chars)
- WARN
examples/ai-sdk/.env.example— .env file present in repo tree — verify it's a template, not real secrets
examples/ai-sdk/.env.example
- WARN
examples/langchain/.env.example— .env file present in repo tree — verify it's a template, not real secrets
examples/langchain/.env.example
- WARN
examples/langchain-js/.env.example— .env file present in repo tree — verify it's a template, not real secrets
examples/langchain-js/.env.example
- WARN
typescript/.env.test.example— .env file present in repo tree — verify it's a template, not real secrets
typescript/.env.test.example
Maintenance
Production sources:
- HIGH
(meta)— Repository is archived — no fixes will be issued upstream
archived
Compatibility
Production sources:
- WARN
(meta)— No engines (Node) or python_requires declared — cross-client compatibility unverified
Documentation
Production sources:
- WARN
(meta)— No SECURITY.md — no disclosure channel for vulnerabilities
missing
- WARN
README— README has no usage/example section
no usage section
- WARN
package.json— package.json missing repository field
no repository
Methodology
SkillAudit v0.2 clones the repo at the provided ref (default: default branch, HEAD) into an ephemeral sandbox, runs six static checks over .js/.ts/.py sources, queries the GitHub API for maintenance signals, and runs an LLM-assisted prompt-injection red-team over the MCP tool surface. Each axis is scored against the rubric at
The prompt-injection axis extracts each server.tool(...) / @app.tool registration + the first ~60 lines of handler body, hands them to Claude Haiku 4.5 with a red-team system prompt, and asks for structured findings on untrusted-content flow into tool responses. One API call per scan, bounded at ~15K input tokens.
How to improve this grade
- Security — static: validate tool-input URLs against an allowlist before fetch/axios calls; use
execFilewith argv arrays instead ofexecwith template strings; never pass untrusted strings tosubprocesswithshell=True. - Security — prompt injection: never return fetched web-page / file / email content verbatim in a tool response. Wrap with a framing marker (e.g.,
<untrusted-content>...</untrusted-content>), summarize rather than inline, and never let untrusted content share a turn with credentials or other tool output. - Credentials findings: redact env-var reads before log lines and error messages; treat any string that ends up in a tool response as public.
- Maintenance: if the repo is inactive, document the maintenance model — "MCP tool, no breaking changes expected" is a legitimate signal.
- Docs: add a README install + usage section with a copy-pasteable command; add a SECURITY.md with a disclosure channel.
_Report generated by skillaudit.dev_
Want your repo audited?
First 100 audits go to waitlist signups in order. The engine runs against public GitHub URLs today.
Join the waitlist →