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.

ykh00046/Server_API

https://github.com/ykh00046/Server_API · scanned 2026-06-16 01:06 UTC (2 months, 1 week ago)

69 raw signals (0 security + 69 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 68 findings

Severity distribution — click a segment to filter

Active filters: severity: info × excluding tests × Reset all

Severity: Critical 0 High 8 Medium 5 Low 49 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 68 Crowd 0 Layer: Software 20 Network 2 Frontend 1 Security 9 Quality 16 Api 20

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 79.3/100 with 88.9% coverage. It contains 1367 nodes across 24 cross-layer flows, written primarily in mixed languages. Engine surfaced 69 findings — concentrated in software (20), api (20), quality (17). Risk profile is high: 0 critical, 8 high, 5 medium. Recommended next step: open the software layer findings first — that's where the highest-impact wins live.

Showing 6 of 68 actionable findings. 69 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.

info System graph quality Integrity conf 1.00 Commented-code block (5 lines) in api/notifications/deliveries_repo.py:28

A long run of `//` or `#` lines usually means abandoned code. Delete or move to git history. Keeps the canvas + dead-code detection honest.

commented codeDead code

info System graph quality Integrity conf 1.00 Commented-code block (5 lines) in shared/cache.py:47

A long run of `//` or `#` lines usually means abandoned code. Delete or move to git history. Keeps the canvas + dead-code detection honest.

commented codeDead code

info System graph quality Integrity conf 1.00 Commented-code block (6 lines) in api/tools/custom.py:168

A long run of `//` or `#` lines usually means abandoned code. Delete or move to git history. Keeps the canvas + dead-code detection honest.

commented codeDead code

info System graph quality Integrity conf 1.00 Commented-code block (8 lines) in tests/test_notifications_async.py:376

A long run of `//` or `#` lines usually means abandoned code. Delete or move to git history. Keeps the canvas + dead-code detection honest.

commented codeDead code

info System graph frontend Coverage conf 1.00 No frontend routes/components detected

No React/Vue/Next routes were found. This is fine for backend-only repos.

info System graph quality Provenance conf 1.00 Very short observed git history

The repo has multiple source files but two or fewer visible commits. This is not a failure by itself, but it lowers confidence in evolution-based diagnosis.

Git historyGenerated repo pattern

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/40c0c09b-2447-4996-b827-7317b6af7fcf/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/40c0c09b-2447-4996-b827-7317b6af7fcf/

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.