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, 2 weeks 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, 2 weeks 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: layer: api × 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

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 60.6/100 with 100.0% coverage. It contains 2682 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 275 findings — concentrated in quality (83), api (72), security (59). Risk profile is high: 1 critical, 22 high, 88 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 72 of 265 actionable findings. 275 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 /sites/${siteId}/memories/${memoryId}/ (mcp-server/src/api.ts:436)

`mcp-server/src/api.ts:436` calls `DELETE /sites/${siteId}/memories/${memoryId}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/sites//memories/` If this points at an external API, prefix it with `ht…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /me/ (mcp-server/src/api.ts:80)

`mcp-server/src/api.ts:80` calls `GET /me/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/me` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /sites/${siteId}/articles/${encodeURIComponent(slug)}/ (mcp-server/src/api.ts:130)

`mcp-server/src/api.ts:130` calls `GET /sites/${siteId}/articles/${encodeURIComponent(slug)}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/sites//articles/` If this points at an external API, prefi…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /sites/${siteId}/articles/${suffix} (mcp-server/src/api.ts:116)

`mcp-server/src/api.ts:116` calls `GET /sites/${siteId}/articles/${suffix}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/sites//articles/` If this points at an external API, prefix it with `https://…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /sites/${siteId}/keywords/ (mcp-server/src/api.ts:203)

`mcp-server/src/api.ts:203` calls `GET /sites/${siteId}/keywords/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/sites//keywords` If this points at an external API, prefix it with `https://` so the matc…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET /sites/${siteId}/seo-score/ (mcp-server/src/api.ts:650)

`mcp-server/src/api.ts:650` calls `GET /sites/${siteId}/seo-score/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/sites//seo-score` If this points at an external API, prefix it with `https://` so the ma…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.gridar.app/api/sites/${siteId}/rss.xml (marketing/components/OnboardingExternalPage.tsx:310)

`marketing/components/OnboardingExternalPage.tsx:310` calls `GET https://api.gridar.app/api/sites/${siteId}/rss.xml` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.gridar.app/api/sites//rss.xml` If thi…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: GET https://api.gridar.app/api/sites/${siteId}/sitemap.xml (marketing/components/OnboardingExternalPage.tsx:295)

`marketing/components/OnboardingExternalPage.tsx:295` calls `GET https://api.gridar.app/api/sites/${siteId}/sitemap.xml` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.gridar.app/api/sites//sitemap.xml…

Dangling fetchFetch

high System graph api Wiring conf 1.00 Dangling fetch: POST /audit/ (mcp-server/src/api.ts:186)

`mcp-server/src/api.ts:186` calls `POST /audit/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/audit` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /brief/ (mcp-server/src/api.ts:193)

`mcp-server/src/api.ts:193` calls `POST /brief/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/brief` If this points at an external API, prefix it with `https://` so the matcher skips it.

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /classify-intent/ (mcp-server/src/api.ts:524)

`mcp-server/src/api.ts:524` calls `POST /classify-intent/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/classify-intent` If this points at an external API, prefix it with `https://` so the matcher skips i…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /link-opportunities/ (mcp-server/src/api.ts:701)

`mcp-server/src/api.ts:701` calls `POST /link-opportunities/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/link-opportunities` If this points at an external API, prefix it with `https://` so the matcher s…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /sites/${siteId}/ai-visibility/run/ (mcp-server/src/api.ts:748)

`mcp-server/src/api.ts:748` calls `POST /sites/${siteId}/ai-visibility/run/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/sites//ai-visibility/run` If this points at an external API, prefix it with `ht…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /sites/${siteId}/generate/ (mcp-server/src/api.ts:155)

`mcp-server/src/api.ts:155` calls `POST /sites/${siteId}/generate/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/sites//generate` If this points at an external API, prefix it with `https://` so the mat…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /sites/${siteId}/keyword-strategy/ (mcp-server/src/api.ts:539)

`mcp-server/src/api.ts:539` calls `POST /sites/${siteId}/keyword-strategy/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/sites//keyword-strategy` If this points at an external API, prefix it with `http…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /sites/${siteId}/keyword-strategy/${strategyId}/approve/ (mcp-server/src/api.ts:561)

`mcp-server/src/api.ts:561` calls `POST /sites/${siteId}/keyword-strategy/${strategyId}/approve/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/sites//keyword-strategy//approve` If this points at an …

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /sites/${siteId}/keywords/snapshot/ (mcp-server/src/api.ts:216)

`mcp-server/src/api.ts:216` calls `POST /sites/${siteId}/keywords/snapshot/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/sites//keywords/snapshot` If this points at an external API, prefix it with `ht…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /sites/${siteId}/landings/manual/ (mcp-server/src/api.ts:597)

`mcp-server/src/api.ts:597` calls `POST /sites/${siteId}/landings/manual/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/sites//landings/manual` If this points at an external API, prefix it with `https:…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /sites/${siteId}/link-pages/ (mcp-server/src/api.ts:635)

`mcp-server/src/api.ts:635` calls `POST /sites/${siteId}/link-pages/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/sites//link-pages` If this points at an external API, prefix it with `https://` so the…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /sites/${siteId}/serp-analyze/ (mcp-server/src/api.ts:314)

`mcp-server/src/api.ts:314` calls `POST /sites/${siteId}/serp-analyze/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/sites//serp-analyze` If this points at an external API, prefix it with `https://` so…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /sites/${siteId}/strategic-opportunities/${opportunityId}/${action}/ (mcp-server/src/api.ts:850)

`mcp-server/src/api.ts:850` calls `POST /sites/${siteId}/strategic-opportunities/${opportunityId}/${action}/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/sites//strategic-opportunities//` If thi…

Dangling fetchHelper:request

high System graph api Wiring conf 1.00 Dangling fetch: POST /sites/${siteId}/strategic-opportunities/refresh/ (mcp-server/src/api.ts:833)

`mcp-server/src/api.ts:833` calls `POST /sites/${siteId}/strategic-opportunities/refresh/` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/sites//strategic-opportunities/refresh` If this points at an exte…

Dangling fetchHelper:request

low System graph api Wiring conf 1.00 Unused endpoint: ANY /accounts/

`backend/config/urls.py` declares `ANY /accounts/` 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: ANY /admin/

`backend/config/urls.py` declares `ANY /admin/` 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: ANY /api/

`backend/config/urls.py` declares `ANY /api/` 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: ANY /api/auth/check-email/

`backend/config/urls.py` declares `ANY /api/auth/check-email/` 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: ANY /api/auth/github/

`backend/config/urls.py` declares `ANY /api/auth/github/` 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: ANY /api/auth/google/

`backend/config/urls.py` declares `ANY /api/auth/google/` 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: ANY /api/auth/logout/

`backend/config/urls.py` declares `ANY /api/auth/logout/` 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: ANY /api/auth/me/

`backend/sites_mgmt/urls.py` declares `ANY /api/auth/me/` 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: ANY /api/auth/password/reset/confirm/

`backend/config/urls.py` declares `ANY /api/auth/password/reset/confirm/` 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: ANY /api/auth/password/reset/request/

`backend/config/urls.py` declares `ANY /api/auth/password/reset/request/` 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: ANY /api/auth/register/

`backend/config/urls.py` declares `ANY /api/auth/register/` 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: ANY /api/auth/token/

`backend/config/urls.py` declares `ANY /api/auth/token/` 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: ANY /api/auth/token/refresh/

`backend/config/urls.py` declares `ANY /api/auth/token/refresh/` 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: ANY /api/branding/scan/

`backend/sites_mgmt/urls.py` declares `ANY /api/branding/scan/` 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: ANY /api/community-questions/

`backend/sites_mgmt/urls.py` declares `ANY /api/community-questions/` 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: ANY /api/image-suggest/

`backend/sites_mgmt/urls.py` declares `ANY /api/image-suggest/` 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: ANY /api/lexicon-check/

`backend/sites_mgmt/urls.py` declares `ANY /api/lexicon-check/` 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: ANY /api/multi-domain-stats/

`backend/sites_mgmt/urls.py` declares `ANY /api/multi-domain-stats/` 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: ANY /api/readability/

`backend/sites_mgmt/urls.py` declares `ANY /api/readability/` 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: ANY /api/shopify/connect/

`backend/sites_mgmt/urls.py` declares `ANY /api/shopify/connect/` 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: ANY /api/shopify/discover/

`backend/sites_mgmt/urls.py` declares `ANY /api/shopify/discover/` 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: ANY /api/sites/<int:site_id>/audit-all/

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/audit-all/` 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: ANY /api/sites/<int:site_id>/broken-links/

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/broken-links/` 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…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/sites/<int:site_id>/cannibalization/

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/cannibalization/` 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 consu…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/sites/<int:site_id>/categories/

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/categories/` 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 i…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/sites/<int:site_id>/content-decay/

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/content-decay/` 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 consume…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/sites/<int:site_id>/keywords/

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/keywords/` 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: ANY /api/sites/<int:site_id>/keywords/<int:pk>/

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/keywords/<int:pk>/` 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 con…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/sites/<int:site_id>/keywords/reclassify/

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/keywords/reclassify/` 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 c…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/sites/<int:site_id>/link-graph/

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/link-graph/` 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 i…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/sites/<int:site_id>/local-business-schema/

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/local-business-schema/` 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…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/sites/<int:site_id>/person-schema/

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/person-schema/` 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 consume…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/sites/<int:site_id>/posts/

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/posts/` 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: ANY /api/sites/<int:site_id>/posts/<slug:slug>/

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/posts/<slug:slug>/` 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 con…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/sites/<int:site_id>/rank-history/

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/rank-history/` 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…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/sites/<int:site_id>/rank-snapshot/

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/rank-snapshot/` 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 consume…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/sites/<int:site_id>/redirects/

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/redirects/` 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: ANY /api/sites/<int:site_id>/redirects/<int:pk>/

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/redirects/<int:pk>/` 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 co…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/sites/<int:site_id>/rss.xml

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/rss.xml` 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: ANY /api/sites/<int:site_id>/sitemap.xml

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/sitemap.xml` 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 i…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/sites/<int:site_id>/stats/

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/stats/` 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: ANY /api/sites/<int:site_id>/tags/

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/tags/` 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: ANY /api/sites/<int:site_id>/topic-clusters/

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/topic-clusters/` 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 consum…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/sites/<int:site_id>/weekly-digest/

`backend/sites_mgmt/urls.py` declares `ANY /api/sites/<int:site_id>/weekly-digest/` 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 consume…

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: ANY /api/trends/

`backend/sites_mgmt/urls.py` declares `ANY /api/trends/` 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: ANY /api/webflow/collections/

`backend/sites_mgmt/urls.py` declares `ANY /api/webflow/collections/` 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: ANY /api/webflow/connect/

`backend/sites_mgmt/urls.py` declares `ANY /api/webflow/connect/` 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: ANY /api/webflow/discover/

`backend/sites_mgmt/urls.py` declares `ANY /api/webflow/discover/` 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: ANY /api/wp/connect/

`backend/sites_mgmt/urls.py` declares `ANY /api/wp/connect/` 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: ANY /api/wp/discover/

`backend/sites_mgmt/urls.py` declares `ANY /api/wp/discover/` 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

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.