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

sequoia-hope/waffle-iron

https://github.com/sequoia-hope/waffle-iron · scanned 2026-06-16 00:07 UTC (2 months, 2 weeks ago)

109 raw signals (0 security + 109 graph)

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

Complete repo analysis

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

JSON
Combined
46.4
/100
Security checks
46
0 findings
System graph
46
100.0% cov · 104 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 18 Medium 15 Low 59 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 104 Crowd 0 Layer: Software 4 Frontend 14 Hardware 3 Security 3 Cicd 2 Quality 59 Api 19
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 46.4/100 with 100.0% coverage. It contains 2911 nodes across 2 cross-layer flows, written primarily in mixed languages. Engine surfaced 109 findings — concentrated in quality (59), api (19), frontend (14). Risk profile is high: 0 critical, 20 high, 15 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 92 of 104 actionable findings. 109 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: DELETE /api/test-cases/${id} (app/tests/gui/test-case-browser.spec.js:53)
`app/tests/gui/test-case-browser.spec.js:53` calls `DELETE /api/test-cases/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/test-cases/<p>` If this points at an external API, prefix it with `https://` so the ma…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /api/test-cases/api-test (app/tests/gui/test-case-browser.spec.js:459)
`app/tests/gui/test-case-browser.spec.js:459` calls `DELETE /api/test-cases/api-test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/test-cases/api-test` If this points at an external API, prefix it with `https://` …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: DELETE /repos/${this.#owner}/${this.#repo}/contents/${path} (app/src/lib/storage/github.js:301)
`app/src/lib/storage/github.js:301` calls `DELETE /repos/${this.#owner}/${this.#repo}/contents/${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/repos/${this.` If this points at an external API, prefi…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/test-cases (app/tests/gui/test-case-browser.spec.js:240)
`app/tests/gui/test-case-browser.spec.js:240` calls `GET /api/test-cases` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/test-cases` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/test-cases (app/tests/gui/test-case-browser.spec.js:433)
`app/tests/gui/test-case-browser.spec.js:433` calls `GET /api/test-cases` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/test-cases` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/test-cases (app/tests/gui/test-case-browser.spec.js:462)
`app/tests/gui/test-case-browser.spec.js:462` calls `GET /api/test-cases` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/test-cases` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/test-cases (app/tests/gui/test-case-browser.spec.js:48)
`app/tests/gui/test-case-browser.spec.js:48` calls `GET /api/test-cases` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/test-cases` If this points at an external API, prefix it with `https://` so the matcher skips i…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/test-cases/api-test (app/tests/gui/test-case-browser.spec.js:441)
`app/tests/gui/test-case-browser.spec.js:441` calls `GET /api/test-cases/api-test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/test-cases/api-test` If this points at an external API, prefix it with `https://` so …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /repos/${this.#owner}/${this.#repo} (app/src/lib/storage/github.js:177)
`app/src/lib/storage/github.js:177` calls `GET /repos/${this.#owner}/${this.#repo}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/repos/${this.` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET /repos/${this.#owner}/${this.#repo}/contents/${path} (app/src/lib/storage/github.js:256)
`app/src/lib/storage/github.js:256` calls `GET /repos/${this.#owner}/${this.#repo}/contents/${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/repos/${this.` If this points at an external API, prefix i…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.github.com/user (app/src/lib/storage/github-auth.js:125)
`app/src/lib/storage/github-auth.js:125` calls `GET https://api.github.com/user` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.github.com/user` If this points at an external API, prefix it with `https://…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /api/test-cases/api-test (app/tests/gui/test-case-browser.spec.js:448)
`app/tests/gui/test-case-browser.spec.js:448` calls `PATCH /api/test-cases/api-test` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/test-cases/api-test` If this points at an external API, prefix it with `https://` s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/test-cases (app/tests/gui/test-case-browser.spec.js:415)
`app/tests/gui/test-case-browser.spec.js:415` calls `POST /api/test-cases` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/test-cases` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/test-cases (app/tests/gui/test-case-browser.spec.js:61)
`app/tests/gui/test-case-browser.spec.js:61` calls `POST /api/test-cases` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/test-cases` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /user/repos (app/src/lib/storage/github.js:180)
`app/src/lib/storage/github.js:180` calls `POST /user/repos` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/user/repos` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: PUT /repos/${this.#owner}/${this.#repo}/contents/${path} (app/src/lib/storage/github.js:277)
`app/src/lib/storage/github.js:277` calls `PUT /repos/${this.#owner}/${this.#repo}/contents/${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/repos/${this.` If this points at an external API, prefix i…
Dangling fetchHelper:apicall
high System graph api Wiring conf 1.00 Dangling fetch: PUT /repos/${this.#owner}/${this.#repo}/contents/${path} (app/src/lib/storage/github.js:284)
`app/src/lib/storage/github.js:284` calls `PUT /repos/${this.#owner}/${this.#repo}/contents/${path}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:apiCall Normalized path used for matching: `/repos/${this.` If this points at an external API, prefix i…
Dangling fetchHelper:apicall
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.
lines 39, 75, 88
Dockerfile:39, 75, 88 (3 hits)
containersRemote installer
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — app/src/lib/engine/assayCaseApi.js:19
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 — app/src/lib/engine/testCaseApi.js:13
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 — app/src/lib/engine/worker.js:19
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 — app/src/lib/storage/github-auth.js:41
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 — app/static/pkg/slvs/slvs.js:1
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 — app/static/pkg/wasm_bridge.js:590
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 — worker/github-oauth-proxy/src/index.js:31
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 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 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/deploy.yml CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in control-api.py:60
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
control-api.py:60 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in crates/slvs-patch/slvs-0.6.0/solvespace/src/platform/html/solvespaceui.js:525
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
crates/slvs-patch/slvs-0.6.0/solvespace/src/platform/html/solvespaceui.js:525 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'node_child_process' in app/vite.config.js:1
Found a known-risky pattern (node_child_process). Review and replace if possible.
app/vite.config.js:1 Node child process
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/auto-waffle/claude-runner.py:65
`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 Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 61 placeholder/mock markers across 20 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 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: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.
Dockerfile:3 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/upload-pages-artifact@v3 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 4 locations
.github/workflows/deploy.yml:43, 56 (2 hits)
.github/workflows/rust-test.yml:57, 66 (2 hits)
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 `maxOld` in app/tests/gui/sketch-entity-deletion.spec.js:312
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: do_GET
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
control-api.py:77
low System graph software Dead code conf 1.00 Possibly dead Python function: do_OPTIONS
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
control-api.py:72
low System graph software Dead code conf 1.00 Possibly dead Python function: do_POST
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
control-api.py:86
low System graph software Dead code conf 1.00 Possibly dead Python function: log_message
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
control-api.py:102
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 — app/src/lib/engine/logger.js:77
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 — app/src/lib/engine/store.svelte.js:781
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 — app/src/lib/engine/worker.js:49
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 — app/src/lib/ui/Toolbar.svelte:154
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 — app/src/lib/viewport/CadModel.svelte:165
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 — app/static/pkg/wasm_bridge.js:329
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 — app/tests/gui/sketch-snap-click-bug.spec.js:88
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 — crates/slvs-patch/slvs-0.6.0/solvespace/src/platform/html/filemanagerui.js:286
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 — crates/slvs-patch/slvs-0.6.0/solvespace/src/platform/html/solvespaceui.js:554
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 — crates/wasm-bridge/js/bridge.js:14
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: USE /api/assay-cases
`app/src/lib/vite-plugins/testCaseApi.js` declares `USE /api/assay-cases` 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: USE /api/test-cases
`app/src/lib/vite-plugins/testCaseApi.js` declares `USE /api/test-cases` 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 quality Complexity conf 1.00 Very large file: app/src/lib/engine/store.svelte.js (4621 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: app/src/lib/sketch/tools.js (1876 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/cherchi-rs/src/arrangements/aux_structure.rs (1327 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/cherchi-rs/src/arrangements/enforce.rs (2156 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/cherchi-rs/src/arrangements/fast_trimesh.rs (2919 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/cherchi-rs/src/arrangements/soup.rs (3116 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/cherchi-rs/src/labeling/inside_out.rs (1669 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/cherchi-rs/src/labeling/inside_out_adversary_tests.rs (1213 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/cherchi-rs/src/predicates/indirect/generated.rs (11958 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/feature-engine/src/rebuild.rs (1848 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/feature-engine/tests/engine_tests.rs (4335 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/indirect-predicates-sidecar-rs/tests/smoke.rs (1452 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/kernel-v2/src/adapter.rs (1849 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/kernel-v2/src/boolean.rs (1770 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/kernel-v2/src/construct.rs (1928 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/kernel-v2/src/tessellate.rs (2134 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/kernel-v2/src/validate.rs (1211 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/sketch-solver/tests/solve_tests.rs (3617 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/ssi-rs/src/lib.rs (1675 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/ssi-rs/tests/ssi3_adversary.rs (1260 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/test-harness/src/assay/gen.rs (4795 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/test-harness/src/assay/randomized_runner.rs (1581 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/test-harness/src/assay/strategies_v2.rs (1649 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/test-harness/src/oracle.rs (2833 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/test-harness/src/workflow.rs (1537 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/waffle-types/src/kernel/mock.rs (2186 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/waffle-types/src/sketch.rs (1701 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/yang-rs/src/lib.rs (9902 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/yang-rs/src/stage0.rs (1347 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/yang-rs/tests/fuzz_curved.rs (1722 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/yang-rs/tests/yr10_stage4_relocate.rs (1611 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/yang-rs/tests/yr21_adversary.rs (1400 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/yang-rs/tests/yr21_cone_ellipse.rs (1585 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/yang-rs/tests/yr22_adversary.rs (1769 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/yang-rs/tests/yr23_cone_hyperbola.rs (1498 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: crates/yang-rs/tests/yr9_stage3_ssi.rs (1491 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/f471c519-1b4e-426b-93d2-5562333f61a3/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f471c519-1b4e-426b-93d2-5562333f61a3/

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.