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.

TokDar2410621/blog-dashboard

https://github.com/TokDar2410621/blog-dashboard · scanned 2026-06-16 00:39 UTC (2 months, 1 week ago)

275 raw signals (0 security + 275 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 265 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 22 Medium 88 Low 88 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 265 Crowd 0 Layer: Software 10 Frontend 49 Security 59 Cicd 2 Quality 73 Api 72

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Duplicates & near-duplicates 9 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

9 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 7 places
low Near-duplicate function bodies in 43 places
low Near-duplicate function bodies in 60 places
low Near-duplicate function bodies in 6 places
low Near-duplicate function bodies in 5 places repo-level
low Near-duplicate function bodies in 4 places
low Near-duplicate function bodies in 26 places
low Near-duplicate function bodies in 37 places

View all duplicates & near-duplicates findings →

Commented-out code 22 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

12 matching findings on this repo

info Commented-code block (6 lines) in marketing/next.config.ts:7
info Commented-code block (7 lines) in marketing/components/StatsCard.tsx:107
info Commented-code block (5 lines) in marketing/components/dashboard/KeywordTracker…
info Commented-code block (9 lines) in marketing/components/dashboard/OverviewPage.t…
info Commented-code block (5 lines) in marketing/components/dashboard/AIGeneratorPag…
info Commented-code block (5 lines) in marketing/components/dashboard/SiteAuditPage.…
info Commented-code block (5 lines) in marketing/components/dashboard/ContentDecayPa…
info Commented-code block (5 lines) in marketing/app/auth/[provider]/callback/page.t…
info Commented-code block (8 lines) in marketing/lib/api-client.ts:1048
info Commented-code block (5 lines) in marketing/context/AuthContext.tsx:31
info Commented-code block (5 lines) in mcp-server/src/api.ts:862
info Commented-code block (6 lines) in mcp-server/src/http.ts:54

View all commented-out code findings →

Config drift 9 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

9 matching findings on this repo

info Commented-code block (6 lines) in marketing/next.config.ts:7
low Stub function `db_for_write` (body is just `pass`/`return`) — backend/config/db…
info Commented-code block (6 lines) in backend/config/auth_views.py:18
info Commented-code block (6 lines) in backend/config/authentication.py:5
info Commented-code block (7 lines) in backend/config/social_auth_views.py:32
info Commented-code block (8 lines) in backend/config/settings.py:141
medium Django CBV `CookieTokenObtainPairView` lacks `LoginRequiredMixin` — backend/con… backend/config/auth_views.py:46
medium Django CBV `CookieTokenRefreshView` lacks `LoginRequiredMixin` — backend/config… backend/config/auth_views.py:66
medium Django CBV `V1AutopilotConfigView` lacks `LoginRequiredMixin` — backend/sites_m… backend/sites_mgmt/api_v1.py:1187

View all config drift findings →

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/37b87ec1-3ea7-4a94-8d90-8d7deb4a3882/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/37b87ec1-3ea7-4a94-8d90-8d7deb4a3882/

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.