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

yangqiang2018/dsv4

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

27 raw signals (1 security + 26 graph)

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

Complete repo analysis

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

JSON
Combined
95.9
/100
Security checks
96
1 findings
System graph
96
66.7% cov · 23 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 0 Medium 4 Low 14 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 1 System graph 23 Crowd 0 Layer: Quality 17 Software 4 Frontend 1 Security 1 Cicd 1
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 95.9/100 with 66.7% coverage. It contains 155 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 26 findings — concentrated in quality (19), software (4), frontend (1). Risk profile is low: 0 critical, 0 high, 3 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 18 of 24 actionable findings. 27 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.

medium Security checks quality Practices conf 0.62 Foundry mined assumption checks: yangqiang2018/dsv4
Comment chain pattern product: assumption_checks Repo: yangqiang2018/dsv4 Thread: yangqiang2018/dsv4#2 Outcome: ambiguous_needs_more_evidence Thread label: thread_needs_classification Source graph label: github_or_motif_graph_without_source_files Reasons: link_quality_weak_supervision Chain evidenc…
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
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 48 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 software Dead code candidate conf 1.00 File has no detected symbols: sparse_attn_sharedkv_tilelang/_tmp_dump_swa.py
Source file with no class/function declarations — possible config, dead code, or scratch file.
low System graph quality Integrity conf 1.00 4 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: mhc_tilelang/verify_mhc_copy.py:main, mhc_tilelang/verify_mhc_copy.py:main This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
4 occurrences
repo-level (4 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: sparse_attn_sharedkv_tilelang/probe_cube_gather.py:probe, sparse_attn_sharedkv_tilelang/probe_cube_gather.py:probe, sparse_attn_sharedkv_tilelang/probe_cube_gather.py:probe This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos …
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 5 places
Functions with the same first-5-line body hash: sparse_attn_sharedkv_tilelang/metadata.py:make, sparse_attn_sharedkv_tilelang/metadata.py:make, sparse_attn_sharedkv_tilelang/metadata.py:make, sparse_attn_sharedkv_tilelang/metadata.py:make This is *the* AI-coder failure mode (4× more duplication in…
duplicatesduplication
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 `row_max_old` in sparse_attn_sharedkv_tilelang/golden.py:188
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 `verify_mhc_copy` in mhc_tilelang/verify_mhc_copy.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 software Dead code conf 1.00 Possibly dead Python function: ascendc_once
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
sparse_attn_sharedkv_perf_compare.py:452
low System graph software Dead code conf 1.00 Possibly dead Python function: tilelang_once
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
sparse_attn_sharedkv_perf_compare.py:384
low System graph software Dead code conf 1.00 Possibly dead Python function: unpack_paged_kv
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
sparse_attn_sharedkv_tilelang/golden.py:247
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: sparse_attn_sharedkv_tilelang/kernel.py (1607 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/e8179183-0a13-417b-90a3-d49280b6e3b0/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/e8179183-0a13-417b-90a3-d49280b6e3b0/

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.