Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.
Sign up free Scan another repo

pwncollege/challenges

https://github.com/pwncollege/challenges · scanned 2026-06-15 23:43 UTC (2 months, 4 weeks ago)

87 raw signals (0 security + 87 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 4 weeks ago · v1 · 70 actionable findings from 1 signal source. 17 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
41.6
/100
Security checks
42
0 findings
System graph
42
100.0% cov · 70 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 13 Medium 29 Low 25 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 70 Crowd 0 Layer: Software 6 Frontend 2 Network 2 Hardware 12 Security 17 Cicd 3 Quality 18 Api 10
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 41.6/100 with 100.0% coverage. It contains 4138 nodes across 10 cross-layer flows, written primarily in mixed languages. Engine surfaced 87 findings — concentrated in hardware (25), quality (18), security (17). Risk profile is high: 0 critical, 13 high, 38 medium. Recommended next step: open the hardware layer findings first — that's where the highest-impact wins live.

Showing 66 of 70 actionable findings. 87 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/skills/authoring-challenges/SKILL.md
Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.
.claude/skills/authoring-challenges/SKILL.md:94 SecretsClaude instruction
high System graph security auth conf 1.00 Flask mutation route `assemble` without `@login_required` — challenges/advent-of-pwn/2025/day-08/challenge/workshop.py:79
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
challenges/advent-of-pwn/2025/day-08/challenge/workshop.py:79 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `block_endpoint` without `@login_required` — challenges/advent-of-pwn/2025/day-06/challenge/north_poole.py:120
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
challenges/advent-of-pwn/2025/day-06/challenge/north_poole.py:120 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `check` without `@login_required` — challenges/advent-of-pwn/2025/day-07/challenge/turkey.py:53
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
challenges/advent-of-pwn/2025/day-07/challenge/turkey.py:53 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `create` without `@login_required` — challenges/advent-of-pwn/2025/day-08/challenge/workshop.py:35
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
challenges/advent-of-pwn/2025/day-08/challenge/workshop.py:35 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `play` without `@login_required` — challenges/advent-of-pwn/2025/day-08/challenge/workshop.py:94
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
challenges/advent-of-pwn/2025/day-08/challenge/workshop.py:94 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `submit_tx` without `@login_required` — challenges/advent-of-pwn/2025/day-06/challenge/north_poole.py:193
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
challenges/advent-of-pwn/2025/day-06/challenge/north_poole.py:193 securityAuth flask unauth route
high System graph security auth conf 1.00 Flask mutation route `tinker` without `@login_required` — challenges/advent-of-pwn/2025/day-08/challenge/workshop.py:52
Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.
challenges/advent-of-pwn/2025/day-08/challenge/workshop.py:52 securityAuth flask unauth route
high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: challenges/linux-luminarium/paths/absolute-cwd-2/challenge/.env
`challenges/linux-luminarium/paths/absolute-cwd-2/challenge/.env` looks like a runtime dotenv file. No high-confidence secret value was matched, but runtime dotenv files often drift into live credentials. Move real values to a secret manager and keep only `.env.example` style templates in source co…
challenges/linux-luminarium/paths/absolute-cwd-2/challenge/.env ConfigEnv fileRuntime env
high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: challenges/linux-luminarium/paths/absolute-cwd/challenge/.env
`challenges/linux-luminarium/paths/absolute-cwd/challenge/.env` looks like a runtime dotenv file. No high-confidence secret value was matched, but runtime dotenv files often drift into live credentials. Move real values to a secret manager and keep only `.env.example` style templates in source cont…
challenges/linux-luminarium/paths/absolute-cwd/challenge/.env ConfigEnv fileRuntime env
high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: challenges/linux-luminarium/paths/relative-dot-local/challenge/.env
`challenges/linux-luminarium/paths/relative-dot-local/challenge/.env` looks like a runtime dotenv file. No high-confidence secret value was matched, but runtime dotenv files often drift into live credentials. Move real values to a secret manager and keep only `.env.example` style templates in sourc…
challenges/linux-luminarium/paths/relative-dot-local/challenge/.env ConfigEnv fileRuntime env
high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: challenges/linux-luminarium/paths/relative-dot/challenge/.env
`challenges/linux-luminarium/paths/relative-dot/challenge/.env` looks like a runtime dotenv file. No high-confidence secret value was matched, but runtime dotenv files often drift into live credentials. Move real values to a secret manager and keep only `.env.example` style templates in source cont…
challenges/linux-luminarium/paths/relative-dot/challenge/.env ConfigEnv fileRuntime env
high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: challenges/linux-luminarium/paths/relative-naked/challenge/.env
`challenges/linux-luminarium/paths/relative-naked/challenge/.env` looks like a runtime dotenv file. No high-confidence secret value was matched, but runtime dotenv files often drift into live credentials. Move real values to a secret manager and keep only `.env.example` style templates in source co…
challenges/linux-luminarium/paths/relative-naked/challenge/.env ConfigEnv fileRuntime env
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — services/registry/src/index.js:2
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph hardware Supply chain conf 1.00 8 occurrences Dockerfile ADD downloads remote content without checksum
Remote build inputs can change or be replaced upstream. Use Dockerfile ADD --checksum or download with an explicit digest/signature verification step.
8 files, 8 locations
challenges/what-is-a-bug/apache-httpd-cve-2014-0117/challenge/Dockerfile:8
challenges/what-is-a-bug/bash-cve-2014-7186/challenge/Dockerfile:19
challenges/what-is-a-bug/libcue-cve-2023-43641/challenge/Dockerfile:3
challenges/what-is-a-bug/libpng-cve-2017-12652/challenge/Dockerfile:3
challenges/what-is-a-bug/libxml-cve-2023-28484/challenge/Dockerfile:3
challenges/what-is-a-bug/mutt-cve-2023-4874/challenge/Dockerfile:3
challenges/what-is-a-bug/readelf-cve-2021-20294/challenge/Dockerfile:3
challenges/what-is-a-bug/sudo-cve-2021-3156/challenge/Dockerfile:2
containersChecksum
medium System graph hardware Security conf 1.00 Dockerfile runs as root: challenges/what-is-a-bug/apache-httpd-cve-2014-0117/challenge/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: challenges/what-is-a-bug/bash-cve-2014-7186/challenge/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: challenges/what-is-a-bug/libcue-cve-2023-43641/challenge/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: challenges/what-is-a-bug/libpng-cve-2017-12652/challenge/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: challenges/what-is-a-bug/libxml-cve-2023-28484/challenge/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: challenges/what-is-a-bug/mutt-cve-2023-4874/challenge/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: challenges/what-is-a-bug/readelf-cve-2021-20294/challenge/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: challenges/what-is-a-bug/sudo-cve-2021-3156/challenge/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned
astral-sh/setup-uv@v7 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 3 locations
.github/workflows/check-maintainers.yml:17
.github/workflows/publish-challenges.yml:47
.github/workflows/sync-maintainers.yml:24
CI/CD securitySupply chainGithub actions
medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions
CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.
.github/workflows/sync-maintainers.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in .github/actions/determine-modified-challenges/action.yml:59
Found a known-risky pattern (node_child_process). Review and replace if possible.
.github/actions/determine-modified-challenges/action.yml:59 Node child process
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in challenges/advent-of-pwn/2025/day-07/challenge/duck.js:3
Found a known-risky pattern (node_child_process). Review and replace if possible.
challenges/advent-of-pwn/2025/day-07/challenge/duck.js:3 Node child process
medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in challenges/advent-of-pwn/2025/day-07/challenge/turkey.py:115
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
challenges/advent-of-pwn/2025/day-07/challenge/turkey.py:115 Subprocess shell true
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — challenges/advent-of-pwn/2025/day-01/challenge/generate_list.py:127
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — challenges/advent-of-pwn/2025/day-06/challenge/children.py:80
`requests.post(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — challenges/advent-of-pwn/2025/day-06/challenge/elf.py:35
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — challenges/advent-of-pwn/2025/day-06/challenge/santa.py:79
`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — challenges/advent-of-pwn/2025/day-07/challenge/turkey.py:115
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — challenges/advent-of-pwn/2025/day-08/challenge/workshop.py:88
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — challenges/advent-of-pwn/2025/day-12/challenge/generate_list.py:205
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — challenges/computing-101/building-a-web-server/common/run.py:120
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — tools/pwnshop/src/pwnshop/commands/run.py:53
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — tools/pwnshop/src/pwnshop/lib/__init__.py:52
`subprocess.check_output(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph network Security conf 1.00 Privileged port 1000 in use
Port 1000 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
challenges/advent-of-pwn/2025/day-06/challenge/init-northpoole.sh Ports
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 46 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: ubuntu:20.04
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
challenges/what-is-a-bug/apache-httpd-cve-2014-0117/challenge/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 7 occurrences Docker base image is tag-pinned but not digest-pinned: ubuntu:24.04
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
7 files, 7 locations
challenges/what-is-a-bug/bash-cve-2014-7186/challenge/Dockerfile:2
challenges/what-is-a-bug/libcue-cve-2023-43641/challenge/Dockerfile:1
challenges/what-is-a-bug/libpng-cve-2017-12652/challenge/Dockerfile:1
challenges/what-is-a-bug/libxml-cve-2023-28484/challenge/Dockerfile:1
challenges/what-is-a-bug/mutt-cve-2023-4874/challenge/Dockerfile:1
challenges/what-is-a-bug/readelf-cve-2021-20294/challenge/Dockerfile:1
challenges/what-is-a-bug/sudo-cve-2021-3156/challenge/Dockerfile:1
containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 3 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/checkout@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 3 locations
.github/workflows/check-maintainers.yml:14
.github/workflows/sync-maintainers.yml:21
.github/workflows/test-challenges.yml:45
CI/CD securitySupply chainGithub actions
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `immutable_file_copy` in challenges/computing-101/building-a-web-server/common/run.py:197
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: check_disassembly
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
challenges/computing-101/common/secret-value-checker.py:86
low System graph software Dead code conf 1.00 Possibly dead Python function: check_runtime
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
challenges/computing-101/common/secret-value-checker.py:184
low System graph software Dead code conf 1.00 Possibly dead Python function: do_GET
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
challenges/what-is-a-bug/apache-httpd-cve-2014-0117/challenge/backend.py:4
low System graph software Dead code conf 1.00 Possibly dead Python function: drop_privs
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
challenges/advent-of-pwn/2025/day-08/challenge/workshop.py:22
low System graph software Dead code conf 1.00 Possibly dead Python function: ignore_git_crypt
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
tools/pwnshop/src/pwnshop/lib/__init__.py:63
low System graph software Dead code conf 1.00 Possibly dead Python function: join_path
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
tools/pwnshop/src/pwnshop/lib/__init__.py:28
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — challenges/advent-of-pwn/2025/day-07/challenge/duck.js:46
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: ANY /
`challenges/advent-of-pwn/2025/day-07/challenge/turkey.py` declares `ANY /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /assemble/<toy_id>
`challenges/advent-of-pwn/2025/day-08/challenge/workshop.py` declares `ANY /assemble/<toy_id>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /balances
`challenges/advent-of-pwn/2025/day-06/challenge/north_poole.py` declares `ANY /balances` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /block
`challenges/advent-of-pwn/2025/day-06/challenge/north_poole.py` declares `ANY /block` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /check
`challenges/advent-of-pwn/2025/day-07/challenge/turkey.py` declares `ANY /check` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /create
`challenges/advent-of-pwn/2025/day-08/challenge/workshop.py` declares `ANY /create` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /play/<toy_id>
`challenges/advent-of-pwn/2025/day-08/challenge/workshop.py` declares `ANY /play/<toy_id>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /tinker/<toy_id>
`challenges/advent-of-pwn/2025/day-08/challenge/workshop.py` declares `ANY /tinker/<toy_id>` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /tx
`challenges/advent-of-pwn/2025/day-06/challenge/north_poole.py` declares `ANY /tx` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /txpool
`challenges/advent-of-pwn/2025/day-06/challenge/north_poole.py` declares `ANY /txpool` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who cons…
Unused endpoint
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/002aebb9-a68c-4723-8e30-c1e2f697d78e/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/002aebb9-a68c-4723-8e30-c1e2f697d78e/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.