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.

QEDGen/qedsvm

https://github.com/QEDGen/qedsvm · scanned 2026-06-15 23:42 UTC (2 months, 4 weeks ago)

23 raw signals (16 security + 7 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

55.6% cov · 7 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 2 Medium 4 Low 3 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 5 System graph 7 Crowd 0 Layer: Quality 9 Security 2 Frontend 1

Exclude dismissed / FP Exclude test files

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 99.1/100 with 55.6% coverage. It contains 281 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 7 findings — concentrated in quality (5), frontend (1), security (1). Risk profile is low: 0 critical, 0 high, 2 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 10 of 12 actionable findings. 49 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.

critical Security checks security auth conf 0.78 11 occurrences Foundry mined security auth guardrail gaps: QEDGen/qedsvm

Graph query export: Security/auth changes without enough guardrails Query id: security_auth_guardrail_gaps Query type: motif_query Intent: Assumption-check security/auth examples requiring stronger tests or CI. Motif: security_auth_without_guardrails Training usage: assumption_check Graph gold labe…

11 occurrences

repo-level (11 hits)

high Security checks quality Quality conf 0.76 2 occurrences Foundry mined schema ui api mismatch: QEDGen/qedsvm

Graph query export: Schema, UI, and API mismatch Query id: schema_ui_api_mismatch Query type: motif_query Intent: Assumption-check examples for data-path consistency across layers. Motif: schema_ui_api_mismatch Training usage: assumption_check Graph gold label: supported_by_verification_signal Repo…

2 occurrences

repo-level (2 hits)

high Security checks quality Testing conf 0.78 7 occurrences Foundry mined test ci gap after feedback: QEDGen/qedsvm

Graph query export: Feedback exposes missing tests or CI Query id: test_ci_gap_after_feedback Query type: motif_query Intent: Hard negatives for feedback/fix chains without adequate guardrails. Motif: test_ci_gap_after_feedback Training usage: hard_negative Graph gold label: supported_by_verificati…

7 occurrences

repo-level (7 hits)

medium Security checks quality Practices conf 0.62 19 occurrences Foundry mined assumption checks: QEDGen/qedsvm

Comment chain pattern product: assumption_checks Repo: QEDGen/qedsvm Thread: QEDGen/qedsvm#9 Outcome: ambiguous_needs_more_evidence Thread label: thread_needs_classification Source graph label: source_artifact_without_verification_graph Reasons: source_graph_has_real_artifacts, link_quality_weak_su…

19 occurrences

repo-level (19 hits)

medium Security checks quality Practices conf 0.70 3 occurrences Foundry mined unresolved feedback: QEDGen/qedsvm

Graph query export: Human feedback without linked fix evidence Query id: unresolved_feedback Query type: motif_query Intent: Negative/unresolved examples that should not be hallucinated into fixes. Motif: unlinked_feedback_needs_evidence Training usage: negative_or_unresolved Graph gold label: weak…

3 occurrences

repo-level (3 hits)

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 security Coverage conf 1.00 No auth library detected

The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.

auth

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 quality Complexity conf 1.00 Very large file: qedsvm-rs/qedrecover/src/main.rs (1740 lines)

Files with >800 lines often hide complexity hotspots and discourage tests.

low System graph quality Complexity conf 1.00 Very large file: qedsvm-rs/tests/diff_mollusk.rs (3723 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/d94ce136-36ba-4c35-90f7-56f9f04e3c85/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d94ce136-36ba-4c35-90f7-56f9f04e3c85/

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.