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

UKGovernmentBEIS/inspect_evals

https://github.com/UKGovernmentBEIS/inspect_evals · scanned 2026-06-16 22:23 UTC (1 month, 2 weeks ago)

1275 raw signals (0 security + 1275 graph)

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

Complete repo analysis

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

JSON
Combined
43.5
/100
Security checks
44
0 findings
System graph
44
100.0% cov · 543 findings
Critical
12
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 12 High 187 Medium 171 Low 138 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 543 Crowd 0 Layer: Software 17 Frontend 4 Network 9 Hardware 141 Security 213 Cicd 1 Quality 119 Api 39
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 43.5/100 with 100.0% coverage. It contains 16011 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 643 findings — concentrated in security (217), hardware (207), quality (136). Risk profile is high: 16 critical, 189 high, 221 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 258 of 543 actionable findings. 643 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 api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1 (src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:61)
`src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:61` calls `GET http://127.0.0.1` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1` If this points …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1/ (src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:63)
`src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:63` calls `GET http://127.0.0.1/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1` If this points…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:1234 (src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:65)
`src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:65` calls `GET http://127.0.0.1:1234` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:1234` If th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://127.0.0.1:1234/abc.txt (src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:67)
`src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:67` calls `GET http://127.0.0.1:1234/abc.txt` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/127.0.0.1:123…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://example.com (src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:45)
`src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:45` calls `GET http://example.com` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com` If this poi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://example.com (src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:47)
`src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:47` calls `GET http://example.com` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/example.com` If this poi…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost (src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:53)
`src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:53` calls `GET http://localhost` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost` If this points …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost/ (src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:55)
`src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:55` calls `GET http://localhost/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost` If this points…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:1234 (src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:57)
`src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:57` calls `GET http://localhost:1234` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:1234` If th…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhost:1234/abc.txt (src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:59)
`src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:59` calls `GET http://localhost:1234/abc.txt` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhost:123…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET http://localhostexample.com (src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:51)
`src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:51` calls `GET http://localhostexample.com` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/http:/localhostexampl…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com (src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:70)
`src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:70` calls `GET https://example.com` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com` If this p…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET https://example.com (src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:72)
`src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:72` calls `GET https://example.com` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/example.com` If this p…
Dangling fetchFetch
high System graph hardware Supply chain conf 1.00 3 occurrences Dockerfile pipes a remote installer into a shell
Executing downloaded code during image build gives the remote endpoint build-time code execution. Prefer pinned packages or verify downloaded installers by checksum/signature.
2 files, 3 locations
src/inspect_evals/scbench/Dockerfile:15, 19 (2 hits)
src/inspect_evals/kernelbench/Dockerfile:15
containersRemote installer
high System graph security security conf 1.00 Insecure pattern 'eval_used' in .claude/skills/code-quality-review-all/SKILL.md:3
Found a known-risky pattern (eval_used). Review and replace if possible.
.claude/skills/code-quality-review-all/SKILL.md:3 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in .claude/skills/security-audit-eval/SKILL.md:35
Found a known-risky pattern (eval_used). Review and replace if possible.
.claude/skills/security-audit-eval/SKILL.md:35 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in README.md:83
Found a known-risky pattern (eval_used). Review and replace if possible.
README.md:83 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in register/ahb/README.md:41
Found a known-risky pattern (eval_used). Review and replace if possible.
register/ahb/README.md:41 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in register/arxivrollbench/README.md:44
Found a known-risky pattern (eval_used). Review and replace if possible.
register/arxivrollbench/README.md:44 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in register/frames/README.md:52
Found a known-risky pattern (eval_used). Review and replace if possible.
register/frames/README.md:52 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in register/hangman-bench/README.md:43
Found a known-risky pattern (eval_used). Review and replace if possible.
register/hangman-bench/README.md:43 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in register/lab_bench_2/README.md:47
Found a known-risky pattern (eval_used). Review and replace if possible.
register/lab_bench_2/README.md:47 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in register/machiavelli/README.md:41
Found a known-risky pattern (eval_used). Review and replace if possible.
register/machiavelli/README.md:41 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in register/mcptox/README.md:46
Found a known-risky pattern (eval_used). Review and replace if possible.
register/mcptox/README.md:46 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in register/medcalc-bench/README.md:46
Found a known-risky pattern (eval_used). Review and replace if possible.
register/medcalc-bench/README.md:46 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in register/tarantubench/README.md:43
Found a known-risky pattern (eval_used). Review and replace if possible.
register/tarantubench/README.md:43 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in src/register_tooling/deriver.py:297
Found a known-risky pattern (eval_used). Review and replace if possible.
src/register_tooling/deriver.py:297 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in tools/dep_bump_impact.py:219
Found a known-risky pattern (eval_used). Review and replace if possible.
tools/dep_bump_impact.py:219 Eval used
high System graph security security conf 1.00 Insecure pattern 'eval_used' in tools/generate_readmes.py:311
Found a known-risky pattern (eval_used). Review and replace if possible.
tools/generate_readmes.py:311 Eval used
high System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in tools/run_evals.py:196
Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.
tools/run_evals.py:196 Subprocess shell true
high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in .claude/skills/security-audit-eval/SKILL.md:109
Found a known-risky pattern (tls_verify_false). Review and replace if possible.
.claude/skills/security-audit-eval/SKILL.md:109 Tls verify false
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/inspect_evals/cybench/challenges/flag_command/images/victim/challenge/application/static/terminal/js/main.js:46
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/inspect_evals/cybench/challenges/glacier_exchange/images/victim/assets/scripts/chart.component.js:25
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/inspect_evals/cybench/challenges/glacier_exchange/images/victim/assets/scripts/index.js:36
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/unencrypted-fetch.js:45
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 authority lacks a verifier contract: .claude/skills/ci-maintenance-workflow/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/ci-maintenance-workflow/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/code-quality-fix-all/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/code-quality-fix-all/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/code-quality-review-all/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/code-quality-review-all/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/create-eval/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/create-eval/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/eval-validity-review/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/eval-validity-review/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/prepare-release/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/prepare-release/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/read-eval-logs/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/read-eval-logs/SKILL.md VerificationClaude instruction
medium System graph security Agent instructions conf 1.00 Agent instruction contains unpinned remote install: .claude/skills/security-audit-eval/SKILL.md
Remote install commands in agent instructions are a supply-chain risk, especially when an agent can execute shell commands.
.claude/skills/security-audit-eval/SKILL.md:80 Supply chainClaude instruction
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Supply chain conf 1.00 38 occurrences Docker base image uses a mutable or implicit tag: aisiuk/inspect-tool-support
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
12 files, 12 locations
src/inspect_evals/theagentcompany/tasks/admin_make_spreadsheet/Dockerfile:1
src/inspect_evals/theagentcompany/tasks/admin_mass_forms_filling/Dockerfile:1
src/inspect_evals/theagentcompany/tasks/admin_remove_pages_pdf/Dockerfile:1
src/inspect_evals/theagentcompany/tasks/admin_translate_sales_chat/Dockerfile:1
src/inspect_evals/theagentcompany/tasks/admin_watch_video/Dockerfile:1
src/inspect_evals/theagentcompany/tasks/ds_answer_numerical_data_question/Dockerfile:1
src/inspect_evals/theagentcompany/tasks/ds_coffee_shop_database_management/Dockerfile:1
src/inspect_evals/theagentcompany/tasks/ds_find_meeting_spreadsheet/Dockerfile:1
containersPinned dependencies
medium System graph hardware Supply chain conf 1.00 3 occurrences Docker base image uses a mutable or implicit tag: alpine:latest
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
3 files, 3 locations
src/inspect_evals/cybench/challenges/delulu/images/victim/Dockerfile:1
src/inspect_evals/threecb/task_configs/null_writing/Dockerfile:1
src/inspect_evals/threecb/task_configs/resourcedevelopment_signing/Dockerfile:1
containersPinned dependencies
medium System graph hardware Security conf 1.00 Dockerfile runs as root: src/inspect_evals/bigcodebench/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: src/inspect_evals/class_eval/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: src/inspect_evals/compute_eval/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: src/inspect_evals/core_bench/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: src/inspect_evals/cybench/agent_sandbox/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: src/inspect_evals/cybench/challenges/avatar/images/victim/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: src/inspect_evals/cybench/challenges/back_to_the_past/images/victim/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: src/inspect_evals/cybench/challenges/chunky/images/blog/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: src/inspect_evals/cybench/challenges/chunky/images/nginx/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: src/inspect_evals/cybench/challenges/chunky/images/rcache/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: src/inspect_evals/cybench/challenges/diffecient/images/victim/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: src/inspect_evals/cybench/challenges/ezmaze/images/victim/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: src/inspect_evals/cybench/challenges/failproof/images/victim/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: src/inspect_evals/cybench/challenges/flag_command/images/victim/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: src/inspect_evals/cybench/challenges/glacier_exchange/images/victim/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: src/inspect_evals/cybench/challenges/just_another_pickle_jail/images/victim/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: src/inspect_evals/cybench/challenges/labyrinth_linguist/images/victim/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: src/inspect_evals/cybench/challenges/locktalk/images/victim/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: src/inspect_evals/cybench/challenges/network_tools/images/victim/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: src/inspect_evals/cybench/challenges/noisier_crc/images/victim/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: src/inspect_evals/cybench/challenges/noisy_crc/images/victim/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: src/inspect_evals/cybench/challenges/robust_cbc/images/victim/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: src/inspect_evals/cybench/challenges/shuffled_aes/images/victim/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: src/inspect_evals/cybench/challenges/skilift/images/victim/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: src/inspect_evals/cybergym/task_template/controller/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: src/inspect_evals/cyberseceval_2/vulnerability_exploit/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: src/inspect_evals/ds1000/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: src/inspect_evals/gdm_in_house_ctf/challenges/attacker/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: src/inspect_evals/gdm_in_house_ctf/challenges/grafana/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: src/inspect_evals/gdm_in_house_ctf/challenges/privesc_7z/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: src/inspect_evals/gdm_in_house_ctf/challenges/privesc_bash/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: src/inspect_evals/gdm_in_house_ctf/challenges/privesc_find/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: src/inspect_evals/gdm_in_house_ctf/challenges/privesc_sed/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: src/inspect_evals/gdm_in_house_ctf/challenges/ssh/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: src/inspect_evals/gdm_in_house_ctf/challenges/webmin/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: src/inspect_evals/gdm_stealth/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: src/inspect_evals/ifevalcode/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: src/inspect_evals/ipi_coding_agent/docker/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: src/inspect_evals/kernelbench/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: src/inspect_evals/mlrc_bench/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: src/inspect_evals/osworld/container/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: src/inspect_evals/paperbench/images/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: src/inspect_evals/scicode/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: src/inspect_evals/theagentcompany/tasks/admin_make_spreadsheet/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: src/inspect_evals/theagentcompany/tasks/admin_mass_forms_filling/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: src/inspect_evals/theagentcompany/tasks/admin_remove_pages_pdf/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: src/inspect_evals/theagentcompany/tasks/admin_translate_sales_chat/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: src/inspect_evals/theagentcompany/tasks/admin_watch_video/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: src/inspect_evals/theagentcompany/tasks/ds_answer_numerical_data_question/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: src/inspect_evals/theagentcompany/tasks/ds_coffee_shop_database_management/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: src/inspect_evals/theagentcompany/tasks/ds_find_meeting_spreadsheet/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: src/inspect_evals/theagentcompany/tasks/ds_fix_table_values_and_missing_answers/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: src/inspect_evals/theagentcompany/tasks/ds_format_excel_sheets/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: src/inspect_evals/theagentcompany/tasks/ds_predictive_modeling/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: src/inspect_evals/theagentcompany/tasks/ds_sql_exercise/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: src/inspect_evals/theagentcompany/tasks/ds_stock_analysis_slides/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: src/inspect_evals/theagentcompany/tasks/ds_visualize_data_in_pie_and_bar_chart/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: src/inspect_evals/theagentcompany/tasks/finance_budget_variance/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: src/inspect_evals/theagentcompany/tasks/finance_check_attendance_payroll/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: src/inspect_evals/theagentcompany/tasks/finance_expense_validation/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: src/inspect_evals/theagentcompany/tasks/finance_invoice_matching/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: src/inspect_evals/theagentcompany/tasks/finance_nonqualified_bill_ask_for_reimburse/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: src/inspect_evals/theagentcompany/tasks/hr_check_attendance_multiple_days/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: src/inspect_evals/theagentcompany/tasks/hr_check_attendance_multiple_days_department/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: src/inspect_evals/theagentcompany/tasks/hr_check_attendance_one_day/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: src/inspect_evals/theagentcompany/tasks/hr_create_employee_manual/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: src/inspect_evals/theagentcompany/tasks/hr_new_grad_job_description/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: src/inspect_evals/theagentcompany/tasks/hr_organize_talent_info/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: src/inspect_evals/theagentcompany/tasks/hr_populate_salary_increase_memo/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: src/inspect_evals/theagentcompany/tasks/hr_resume_categorization/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: src/inspect_evals/theagentcompany/tasks/hr_salary_analysis/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: src/inspect_evals/theagentcompany/tasks/ml_generate_gradcam/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: src/inspect_evals/theagentcompany/tasks/ml_grade_exam/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: src/inspect_evals/theagentcompany/tasks/research_answer_questions_on_paper/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: src/inspect_evals/theagentcompany/tasks/sde_copy_table_from_pdf_to_xlsx/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: src/inspect_evals/theagentcompany/tasks/sde_create_sqlite_database/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: src/inspect_evals/theagentcompany/tasks/sde_run_rising_wave_locally/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: src/inspect_evals/theagentcompany/tasks/test_basic_llm_judge/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: src/inspect_evals/theagentcompany/tasks/test_evaluator_helpers/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: src/inspect_evals/theagentcompany/tasks/test_install_permissions/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: src/inspect_evals/theagentcompany/tasks/test_owncloud_file_reading/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: src/inspect_evals/threecb/task_configs/binpwn_gdb_repl/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: src/inspect_evals/threecb/task_configs/evasion_debugger/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: src/inspect_evals/threecb/task_configs/find_all_users/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: src/inspect_evals/threecb/task_configs/impact_defacing/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: src/inspect_evals/threecb/task_configs/initialaccess_mail_link/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: src/inspect_evals/threecb/task_configs/nmap/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: src/inspect_evals/threecb/task_configs/python_repl_factorial10/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: src/inspect_evals/threecb/task_configs/resourcedevelopment_signing/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: src/inspect_evals/threecb/task_configs/web_navigation/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: src/inspect_evals/vimgolf_challenges/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: tests/utils/test_artifacts/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 12 occurrences 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.
12 files, 12 locations
.github/workflows/build-repo-context.yaml
.github/workflows/claude-fix-tests.yaml
.github/workflows/claude-issue-solver.yaml
.github/workflows/claude-review.yaml
.github/workflows/docs-preview.yml
.github/workflows/docs.yml
.github/workflows/publish.yaml
.github/workflows/register-issue-submission.yaml
CI/CD securitySupply chainGithub actions
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — .github/scripts/run_targeted_tests.py:100
`subprocess.Popen(...)` 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 — src/inspect_evals/bfcl/backends/downloader.py:13
`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 — src/inspect_evals/bfcl/data.py:59
`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 — src/inspect_evals/core_bench/dataset.py:220
`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 — src/inspect_evals/cti_realm/docker/mitre_service/mitre_loader.py:45
`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 — src/inspect_evals/cybench/challenges/chunky/images/blog/src/admin/admin.py:17
`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 — src/inspect_evals/cybench/challenges/locktalk/solution/solve.py:77
`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 — src/inspect_evals/cybergym/task_template/executor/http_entrypoint.py:86
`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 — src/inspect_evals/cyberseceval_2/vulnerability_exploit/challenges/memory_corruption/examples.py:308
`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 — src/inspect_evals/cyberseceval_4/autonomous_uplift/dataset.py:19
`urllib.request.urlopen(...)` 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 — src/inspect_evals/cyberseceval_4/autopatching/dataset.py:16
`urllib.request.urlopen(...)` 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 — src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/python/subprocess_using_shell.py:11
`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 — src/inspect_evals/mlrc_bench/dataset.py:290
`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 — src/inspect_evals/mlrc_bench/orig_benchmark_corrections/product-rec/scripts/prepare.py:13
`subprocess.Popen(...)` 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 — src/inspect_evals/osworld/container/code/config.py:111
`subprocess.Popen(...)` 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 — src/inspect_evals/osworld/sparse_clone.py:34
`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 — src/inspect_evals/utils/docker_utils.py:22
`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/check_undeclared_assets.py:12
`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 — tools/debug_sandbox.py:151
`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/dep_bump_impact.py:30
`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/generate_asset_manifest.py:26
`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/run_evals.py:196
`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 Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 64 placeholder/mock markers across 37 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Maintenance conf 1.00 43 TODO/FIXME markers
High count of TODO/FIXME/HACK markers — track them as issues so they're not forgotten.
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 704 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 3 occurrences Docker base image is tag-pinned but not digest-pinned: debian:bookworm-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
2 files, 3 locations
src/inspect_evals/cybench/challenges/skilift/images/victim/Dockerfile:3, 22 (2 hits)
src/inspect_evals/cybench/challenges/walking_to_the_sea_side/images/walking-to-the-sea-side/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: debian:stable
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
src/inspect_evals/threecb/task_configs/binpwn_gdb_repl/Dockerfile:1
src/inspect_evals/threecb/task_configs/escalation_setuid/Dockerfile:1
src/inspect_evals/threecb/task_configs/impact_defacing/Dockerfile:1
src/inspect_evals/threecb/task_configs/initialaccess_mail_link/Dockerfile:1
src/inspect_evals/threecb/task_configs/nmap/Dockerfile:1
src/inspect_evals/threecb/task_configs/python_repl_factorial10/Dockerfile:1
src/inspect_evals/threecb/task_configs/web_navigation/Dockerfile:1
containersPinned dependencies
low System graph hardware Supply chain conf 1.00 4 occurrences Docker base image is tag-pinned but not digest-pinned: debian:trixie-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
4 files, 4 locations
src/inspect_evals/gdm_in_house_ctf/challenges/privesc_7z/Dockerfile:1
src/inspect_evals/gdm_in_house_ctf/challenges/privesc_bash/Dockerfile:1
src/inspect_evals/gdm_in_house_ctf/challenges/privesc_find/Dockerfile:1
src/inspect_evals/gdm_in_house_ctf/challenges/privesc_sed/Dockerfile:1
containersPinned dependencies
low System graph hardware Supply chain conf 1.00 4 occurrences Docker base image is tag-pinned but not digest-pinned: python:3-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
4 files, 4 locations
src/inspect_evals/gdm_in_house_ctf/challenges/cmd_injection/Dockerfile:1
src/inspect_evals/gdm_in_house_ctf/challenges/idor/Dockerfile:1
src/inspect_evals/gdm_in_house_ctf/challenges/spray/Dockerfile:1
src/inspect_evals/gdm_in_house_ctf/challenges/sqli/Dockerfile:1
containersPinned dependencies
low System graph hardware Supply chain conf 1.00 4 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.10-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
4 files, 4 locations
src/inspect_evals/bigcodebench/Dockerfile:6
src/inspect_evals/ds1000/Dockerfile:2
src/inspect_evals/ifevalcode/Dockerfile:1
tests/utils/test_artifacts/Dockerfile:1
containersPinned dependencies
low System graph hardware Supply chain conf 1.00 6 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.9-slim-buster
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
6 files, 6 locations
src/inspect_evals/cybench/challenges/diffecient/images/victim/Dockerfile:1
src/inspect_evals/cybench/challenges/ezmaze/images/victim/Dockerfile:1
src/inspect_evals/cybench/challenges/failproof/images/victim/Dockerfile:1
src/inspect_evals/cybench/challenges/noisier_crc/images/victim/Dockerfile:1
src/inspect_evals/cybench/challenges/noisy_crc/images/victim/Dockerfile:1
src/inspect_evals/cybench/challenges/randsubware/images/victim/Dockerfile:1
containersPinned dependencies
low System graph hardware Supply chain conf 1.00 4 occurrences 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.
3 files, 4 locations
src/inspect_evals/mle_bench/Dockerfile:2, 19 (2 hits)
src/inspect_evals/cybench/challenges/chunky/images/blog/Dockerfile:1
src/inspect_evals/cybench/challenges/network_tools/images/victim/Dockerfile:1
containersPinned dependencies
low System graph quality Integrity conf 1.00 16 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: tools/create_markdown_files_from_trajectories.py:format_content_item, tools/create_markdown_files_from_trajectories.py:format_content This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). C…
16 occurrences
repo-level (16 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: tools/run_autolint/checks/best_practices.py:visit_FunctionDef, tools/run_autolint/checks/best_practices.py:visit_FunctionDef, tools/run_autolint/checks/best_practices.py:visit_FunctionDef This is *the* AI-coder failure mode (4× more duplication in vi…
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: src/inspect_evals/agentdojo/tools/cloud_drive_client.py:search_files_by_filename, src/inspect_evals/agentdojo/tools/cloud_drive_client.py:search_files, src/inspect_evals/agentdojo/tools/cloud_drive_client.py:search_files_by_filename, src/inspect_evals…
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `file_backup` in src/inspect_evals/agentharm/benchmark/benign_tools/query_google_search.py:29
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 quality Integrity conf 1.00 Old/deprecated-named symbol `metric_result_copy` in src/inspect_evals/fortress/scorer.py:114
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 quality Integrity conf 1.00 Old/deprecated-named symbol `mock_backup` in tests/mlrc_bench/test_mlrc_high_level_actions.py:117
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 quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in src/inspect_evals/bbh/bbh.py:136
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 quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in src/inspect_evals/bbq/bbq.py:120
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 quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in src/inspect_evals/cybench/cybench.py:127
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 quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in src/inspect_evals/paperbench/score/task_node.py:168
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 quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in src/inspect_evals/tau2/telecom/TelecomUserTools.py:589
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 quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in tests/agentdojo/test_deepdiff_wrappers.py:54
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 quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in tools/report_utils.py:552
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 quality Integrity conf 1.00 Old/deprecated-named symbol `model_results_copy` in src/inspect_evals/bfcl/score/multi_turn_scorer.py:323
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 quality Integrity conf 1.00 Old/deprecated-named symbol `nonOld` in tests/bbq/test_bbq.py:80
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 quality Integrity conf 1.00 Old/deprecated-named symbol `remove_revoked_deprecated` in src/inspect_evals/cti_realm/docker/mitre_service/mitre_loader.py:65
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 quality Integrity conf 1.00 Old/deprecated-named symbol `run_backup` in src/inspect_evals/agentharm/benchmark/benign_grading_functions.py:2955
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 quality Integrity conf 1.00 Old/deprecated-named symbol `run_backup` in src/inspect_evals/agentharm/benchmark/benign_tools/get_webpage.py:871
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 quality Integrity conf 1.00 Old/deprecated-named symbol `run_backup` in src/inspect_evals/agentharm/benchmark/benign_tools/terminal.py:68
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 quality Integrity conf 1.00 Old/deprecated-named symbol `sec_qa_v1` in src/inspect_evals/_registry.py:229
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 quality Integrity conf 1.00 Old/deprecated-named symbol `sec_qa_v1` in src/inspect_evals/sec_qa/__init__.py:6
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 quality Integrity conf 1.00 Old/deprecated-named symbol `sec_qa_v1` in tests/sec_qa/test_sec_qa.py:7
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 quality Integrity conf 1.00 Old/deprecated-named symbol `secqa_v1` in src/inspect_evals/sec_qa/sec_qa.py:28
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 quality Integrity conf 1.00 Old/deprecated-named symbol `secqa_v1` in tests/sec_qa/test_sec_qa_dataset.py:18
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 quality Integrity conf 1.00 Old/deprecated-named symbol `signature_copy` in src/inspect_evals/cyberseceval_4/malware_analysis.py:336
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 quality Integrity conf 1.00 Old/deprecated-named symbol `squad_v2` in src/inspect_evals/abstention_bench/recipe/abstention_datasets/squad.py:22
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 quality Integrity conf 1.00 Old/deprecated-named symbol `squad_v2` in src/inspect_evals/squad/squad.py:24
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 quality Integrity conf 1.00 Old/deprecated-named symbol `squad_v2` in tests/squad/test_squad.py:80
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 quality Integrity conf 1.00 Old/deprecated-named symbol `test_ds_predictive_modeling_checkpoint_thresholds_match_legacy` in tests/theagentcompany/test_scorers.py:149
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 quality Integrity conf 1.00 Old/deprecated-named symbol `test_undo_edit_script_no_backup` in tests/mlrc_bench/test_mlrc_low_level_actions.py:108
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 quality Integrity conf 1.00 Old/deprecated-named symbol `usaco_v2` in src/inspect_evals/usaco/dataset.py:98
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 quality Integrity conf 1.00 Old/deprecated-named symbol `usaco_v2` in src/inspect_evals/usaco/usaco.py:112
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 quality Integrity conf 1.00 Old/deprecated-named symbol `web_of_lies_v2` in src/inspect_evals/livebench/scorer.py:44
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 quality Integrity conf 1.00 Old/deprecated-named symbol `web_of_lies_v2` in tests/livebench/test_decide_scorer.py:33
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 quality Integrity conf 1.00 Old/deprecated-named symbol `web_of_lies_v2` in tests/livebench/test_record_to_sample.py:182
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: is_sample_failed
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
tools/create_markdown_files_from_trajectories.py:443
low System graph software Dead code conf 1.00 3 occurrences Possibly dead Python function: placeholder_ground_truth
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
3 files, 3 locations
src/inspect_evals/agentdojo/task_suites/banking/injection_tasks.py:561
src/inspect_evals/agentdojo/task_suites/travel/injection_tasks.py:408
src/inspect_evals/agentdojo/task_suites/workspace_plus/injection_tasks.py:30
low System graph software Dead code conf 1.00 Possibly dead Python function: replace_repo_root_path
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
tools/generate_readmes.py:926
low System graph software Dead code conf 1.00 Possibly dead Python function: replace_windows_path
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
tools/generate_readmes.py:958
low System graph software Dead code conf 1.00 Possibly dead Python function: run_eval_job
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
tools/run_evals.py:274
low System graph software Dead code conf 1.00 Possibly dead Python function: set_multiline_output
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.github/scripts/register_submission/_github.py:137
low System graph software Dead code conf 1.00 Possibly dead Python function: smoke_test
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
tools/run_evals.py:215
low System graph software Dead code conf 1.00 Possibly dead Python function: visit_Attribute
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
tools/check_posix_code.py:94
low System graph software Dead code conf 1.00 Possibly dead Python function: visit_Call
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
tools/check_posix_code.py:128
low System graph software Dead code conf 1.00 Possibly dead Python function: visit_Call
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
tools/run_autolint/checks/best_practices.py:169
low System graph software Dead code conf 1.00 Possibly dead Python function: visit_FunctionDef
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
tools/run_autolint/checks/best_practices.py:240
low System graph software Dead code conf 1.00 Possibly dead Python function: visit_Import
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
tools/check_posix_code.py:106
low System graph software Dead code conf 1.00 Possibly dead Python function: visit_ImportFrom
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
tools/check_posix_code.py:114
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/inspect_evals/cybench/challenges/flag_command/images/victim/challenge/application/static/terminal/js/main.js:55
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/child-process.js:13
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 frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — src/inspect_evals/cyberseceval_4/insecure_code_detector/rules/semgrep/javascript/third-party/eval-usage.js:6
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 quality Integrity conf 1.00 Stub function `deescalate_time_passes` (body is just `pass`/`return`) — src/inspect_evals/gdm_stealth/solver/strategic_rule_breaking/oversight.py:221
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph quality Integrity conf 1.00 Stub function `get_grader_input` (body is just `pass`/`return`) — src/inspect_evals/agentic_misalignment/classifiers/classifier.py:20
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph api Wiring conf 1.00 Unused endpoint: ANY /
`src/inspect_evals/cybench/challenges/locktalk/images/victim/challenge/app/main/routes.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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /<user_id>/.well-known/jwks.json
`src/inspect_evals/cybench/challenges/chunky/images/blog/src/app.py` declares `ANY /<user_id>/.well-known/jwks.json` 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 re…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /about
`src/inspect_evals/gdm_in_house_ctf/challenges/cmd_injection/app.py` declares `ANY /about` 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 /accounts
`src/inspect_evals/gdm_in_house_ctf/challenges/idor/app.py` declares `ANY /accounts` 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 consum…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/data/fetch/<path:coin>
`src/inspect_evals/cybench/challenges/glacier_exchange/images/victim/server.py` declares `ANY /api/data/fetch/<path:coin>` 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 — consi…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /assets/<path:path>
`src/inspect_evals/cybench/challenges/glacier_exchange/images/victim/server.py` declares `ANY /assets/<path:path>` 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 remo…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /chat/<int:chat_id>
`src/inspect_evals/cybench/challenges/locktalk/images/victim/challenge/app/api/routes.py` declares `ANY /chat/<int:chat_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 — con…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /create_post
`src/inspect_evals/cybench/challenges/chunky/images/blog/src/app.py` declares `ANY /create_post` 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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /creds
`src/inspect_evals/gdm_in_house_ctf/challenges/idor/app.py` declares `ANY /creds` 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 /creds/<account_id>
`src/inspect_evals/gdm_in_house_ctf/challenges/idor/app.py` declares `ANY /creds/<account_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 /flag
`src/inspect_evals/cybench/challenges/locktalk/images/victim/challenge/app/api/routes.py` declares `ANY /flag` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /get_ticket
`src/inspect_evals/cybench/challenges/locktalk/images/victim/challenge/app/api/routes.py` declares `ANY /get_ticket` 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 re…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /home
`src/inspect_evals/gdm_in_house_ctf/challenges/idor/app.py` declares `ANY /home` 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 /login
`src/inspect_evals/cybench/challenges/chunky/images/blog/src/app.py` declares `ANY /login` 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 /logout
`src/inspect_evals/cybench/challenges/chunky/images/blog/src/app.py` declares `ANY /logout` 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 /models
`src/inspect_evals/gdm_in_house_ctf/challenges/sqli/app.py` declares `ANY /models` 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 /network
`src/inspect_evals/gdm_in_house_ctf/challenges/cmd_injection/app.py` declares `ANY /network` 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 /post/<user_id>/<post_id>
`src/inspect_evals/cybench/challenges/chunky/images/blog/src/app.py` declares `ANY /post/<user_id>/<post_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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: ANY /sample
`src/inspect_evals/gdm_in_house_ctf/challenges/sqli/app.py` declares `ANY /sample` 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 /signup
`src/inspect_evals/cybench/challenges/chunky/images/blog/src/app.py` declares `ANY /signup` 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 /users
`src/inspect_evals/gdm_in_house_ctf/challenges/sqli/app.py` declares `ANY /users` 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 /users/<login>
`src/inspect_evals/gdm_in_house_ctf/challenges/sqli/app.py` declares `ANY /users/<login>` 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 c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /search/{keyword}
`src/inspect_evals/cti_realm/docker/mitre_service/mitre_api.py` declares `GET /search/{keyword}` 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 documentin…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /tactic/{tactic}
`src/inspect_evals/cti_realm/docker/mitre_service/mitre_api.py` declares `GET /tactic/{tactic}` 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: POST /submit-fixed
`src/inspect_evals/cybergym/task_template/controller/server.py` declares `POST /submit-fixed` 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 w…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /submit-vulnerable
`src/inspect_evals/cybergym/task_template/controller/server.py` declares `POST /submit-vulnerable` 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 document…
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: src/inspect_evals/agentdojo/task_suites/travel/user_tasks.py (2371 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/inspect_evals/agentdojo/task_suites/workspace/user_tasks.py (1588 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/inspect_evals/agentharm/benchmark/benign_grading_functions.py (3233 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/inspect_evals/agentharm/benchmark/benign_tools/get_webpage.py (2340 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/inspect_evals/agentharm/benchmark/harmful_grading_functions.py (3029 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/inspect_evals/agentharm/benchmark/harmful_tools/get_webpage.py (2545 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/inspect_evals/persistbench/prompts.py (1640 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/inspect_evals/tau2/banking/BankingAgentTools.py (3432 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/13d59e23-a6db-41ca-bf82-51b9ab36f8d1/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/13d59e23-a6db-41ca-bf82-51b9ab36f8d1/

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.