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

raniel90/obione

https://github.com/raniel90/obione · scanned 2026-06-15 23:46 UTC (2 months, 4 weeks ago)

206 raw signals (0 security + 206 graph)

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

Complete repo analysis

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

JSON
Combined
51.1
/100
Security checks
51
0 findings
System graph
51
100.0% cov · 163 findings
Critical
3
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 3 High 71 Medium 19 Low 59 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 163 Crowd 0 Layer: Software 5 Frontend 8 Hardware 5 Security 18 Quality 29 Api 98
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 51.1/100 with 100.0% coverage. It contains 2571 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 206 findings — concentrated in api (98), quality (47), software (30). Risk profile is high: 3 critical, 71 high, 19 medium. Recommended next step: open the api layer findings first — that's where the highest-impact wins live.

Showing 151 of 163 actionable findings. 206 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 System graph security Secrets conf 1.00 Possible secret in backend/v1/src/obione/cli/seed_demo.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
backend/v1/src/obione/cli/seed_demo.py:44
critical System graph security Secrets conf 1.00 Possible secret in frontend/v1/e2e/helpers.ts
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
frontend/v1/e2e/helpers.ts:4
critical System graph security Secrets conf 1.00 Possible secret in frontend/v1/src/pages/LoginPage.tsx
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
frontend/v1/src/pages/LoginPage.tsx:21
high System graph api Wiring conf 1.00 Dangling fetch: GET /ai/stats (frontend/src/services/aiService.ts:110)
`frontend/src/services/aiService.ts:110` calls `GET /ai/stats` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/ai/stats` 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 /auth/me (frontend/src/services/authService.ts:42)
`frontend/src/services/authService.ts:42` calls `GET /auth/me` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/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 /community (frontend/src/services/communityService.ts:22)
`frontend/src/services/communityService.ts:22` calls `GET /community` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/community` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /community/domains/${domainId} (frontend/src/services/communityService.ts:60)
`frontend/src/services/communityService.ts:60` calls `GET /community/domains/${domainId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/community/domains/<p>` If this points at an external API, prefix it w…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /community/domains/slug/${slug} (frontend/src/services/communityService.ts:38)
`frontend/src/services/communityService.ts:38` calls `GET /community/domains/slug/${slug}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/community/domains/slug/<p>` If this points at an external API, prefi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /discussions (frontend/src/services/discussionService.ts:160)
`frontend/src/services/discussionService.ts:160` calls `GET /discussions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/discussions` 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 /discussions/${discussionId}/knowledge (frontend/src/services/knowledgeService.ts:119)
`frontend/src/services/knowledgeService.ts:119` calls `GET /discussions/${discussionId}/knowledge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/discussions/<p>/knowledge` If this points at an external API…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /discussions/${id} (frontend/src/services/discussionService.ts:166)
`frontend/src/services/discussionService.ts:166` calls `GET /discussions/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/discussions/<p>` If this points at an external API, prefix it with `https://` s…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /domains (frontend/src/services/domainService.ts:6)
`frontend/src/services/domainService.ts:6` calls `GET /domains` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/domains` 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 /domains/${domainId}/discussions (frontend/src/services/discussionService.ts:174)
`frontend/src/services/discussionService.ts:174` calls `GET /domains/${domainId}/discussions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/domains/<p>/discussions` If this points at an external API, prefi…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /domains/${domainId}/knowledge (frontend/src/services/knowledgeService.ts:109)
`frontend/src/services/knowledgeService.ts:109` calls `GET /domains/${domainId}/knowledge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/domains/<p>/knowledge` If this points at an external API, prefix it …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /domains/${domainId}/phenomena (frontend/src/services/phenomenonService.ts:68)
`frontend/src/services/phenomenonService.ts:68` calls `GET /domains/${domainId}/phenomena` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/domains/<p>/phenomena` If this points at an external API, prefix it …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /domains/${id} (frontend/src/services/domainService.ts:12)
`frontend/src/services/domainService.ts:12` calls `GET /domains/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/domains/<p>` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /domains/slug/${slug} (frontend/src/services/domainService.ts:21)
`frontend/src/services/domainService.ts:21` calls `GET /domains/slug/${slug}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/domains/slug/<p>` 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: GET /knowledge (frontend/src/services/knowledgeService.ts:95)
`frontend/src/services/knowledgeService.ts:95` calls `GET /knowledge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/knowledge` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /knowledge/${id} (frontend/src/services/knowledgeService.ts:101)
`frontend/src/services/knowledgeService.ts:101` calls `GET /knowledge/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/knowledge/<p>` 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: GET /mpo/attributes (frontend/src/services/mpoAttributeService.ts:29)
`frontend/src/services/mpoAttributeService.ts:29` calls `GET /mpo/attributes` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/mpo/attributes` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /mpo/categories (frontend/src/services/mpoAttributeService.ts:35)
`frontend/src/services/mpoAttributeService.ts:35` calls `GET /mpo/categories` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/mpo/categories` If this points at an external API, prefix it with `https://` so t…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /observations/${id} (frontend/src/services/observationService.ts:61)
`frontend/src/services/observationService.ts:61` calls `GET /observations/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/observations/<p>` 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 /permissions (frontend/src/services/governanceService.ts:12)
`frontend/src/services/governanceService.ts:12` calls `GET /permissions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/permissions` If this points at an external API, prefix it with `https://` so the match…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /phenomena (frontend/src/services/phenomenonService.ts:49)
`frontend/src/services/phenomenonService.ts:49` calls `GET /phenomena` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/phenomena` 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: GET /phenomena/${id} (frontend/src/services/phenomenonService.ts:55)
`frontend/src/services/phenomenonService.ts:55` calls `GET /phenomena/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/phenomena/<p>` 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: GET /profile-permissions (frontend/src/services/governanceService.ts:17)
`frontend/src/services/governanceService.ts:17` calls `GET /profile-permissions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/profile-permissions` 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 /profiles (frontend/src/services/profileService.ts:7)
`frontend/src/services/profileService.ts:7` calls `GET /profiles` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/profiles` 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: GET /profiles/${code} (frontend/src/services/profileService.ts:13)
`frontend/src/services/profileService.ts:13` calls `GET /profiles/${code}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/profiles/<p>` 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 /projects (frontend/src/services/projectService.ts:66)
`frontend/src/services/projectService.ts:66` calls `GET /projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects` If this points at an external API, prefix it with `https://` so the matcher skips …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /projects/${id} (frontend/src/services/projectService.ts:96)
`frontend/src/services/projectService.ts:96` calls `GET /projects/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>` 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 /projects/${id}/coverage (frontend/src/services/projectService.ts:88)
`frontend/src/services/projectService.ts:88` calls `GET /projects/${id}/coverage` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/coverage` If this points at an external API, prefix it with `htt…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /projects/${projectId}/discussions (frontend/src/services/discussionService.ts:179)
`frontend/src/services/discussionService.ts:179` calls `GET /projects/${projectId}/discussions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/discussions` If this points at an external API, pr…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /projects/${projectId}/knowledge (frontend/src/services/knowledgeService.ts:114)
`frontend/src/services/knowledgeService.ts:114` calls `GET /projects/${projectId}/knowledge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/knowledge` If this points at an external API, prefix …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /projects/${projectId}/observations (frontend/src/services/observationService.ts:55)
`frontend/src/services/observationService.ts:55` calls `GET /projects/${projectId}/observations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/observations` If this points at an external API, …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /projects/${projectId}/phenomena (frontend/src/services/phenomenonService.ts:63)
`frontend/src/services/phenomenonService.ts:63` calls `GET /projects/${projectId}/phenomena` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/phenomena` If this points at an external API, prefix …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /projects/domain/${domainId} (frontend/src/services/projectService.ts:104)
`frontend/src/services/projectService.ts:104` calls `GET /projects/domain/${domainId}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/domain/<p>` If this points at an external API, prefix it with `…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: GET /users/${id} (frontend/src/services/userService.ts:12)
`frontend/src/services/userService.ts:12` calls `GET /users/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/users/<p>` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /observations/${id}/analyze (frontend/src/services/observationService.ts:96)
`frontend/src/services/observationService.ts:96` calls `PATCH /observations/${id}/analyze` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/observations/<p>/analyze` If this points at an external API, prefix …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PATCH /projects/${id}/status (frontend/src/services/projectService.ts:135)
`frontend/src/services/projectService.ts:135` calls `PATCH /projects/${id}/status` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/status` 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 /ai/project-setup (frontend/src/services/aiService.ts:82)
`frontend/src/services/aiService.ts:82` calls `POST /ai/project-setup` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/ai/project-setup` 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: POST /auth/login (frontend/src/services/authService.ts:12)
`frontend/src/services/authService.ts:12` calls `POST /auth/login` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/login` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /auth/logout (frontend/src/services/authService.ts:33)
`frontend/src/services/authService.ts:33` calls `POST /auth/logout` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/auth/logout` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /discussions (frontend/src/services/discussionService.ts:186)
`frontend/src/services/discussionService.ts:186` calls `POST /discussions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/discussions` 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 /discussions/${discussionId}/ai/suggest-knowledge (frontend/src/services/aiService.ts:57)
`frontend/src/services/aiService.ts:57` calls `POST /discussions/${discussionId}/ai/suggest-knowledge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/discussions/<p>/ai/suggest-knowledge` If this points at …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /discussions/${discussionId}/consolidate (frontend/src/services/knowledgeService.ts:137)
`frontend/src/services/knowledgeService.ts:137` calls `POST /discussions/${discussionId}/consolidate` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/discussions/<p>/consolidate` If this points at an externa…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /discussions/${discussionId}/contributions (frontend/src/services/discussionService.ts:198)
`frontend/src/services/discussionService.ts:198` calls `POST /discussions/${discussionId}/contributions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/discussions/<p>/contributions` If this points at an ex…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /discussions/${id}/archive (frontend/src/services/discussionService.ts:228)
`frontend/src/services/discussionService.ts:228` calls `POST /discussions/${id}/archive` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/discussions/<p>/archive` If this points at an external API, prefix it …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /domains (frontend/src/services/domainService.ts:29)
`frontend/src/services/domainService.ts:29` calls `POST /domains` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/domains` 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 /domains/${domainId}/ai/synthesize (frontend/src/services/aiService.ts:64)
`frontend/src/services/aiService.ts:64` calls `POST /domains/${domainId}/ai/synthesize` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/domains/<p>/ai/synthesize` If this points at an external API, prefix it…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /knowledge (frontend/src/services/knowledgeService.ts:126)
`frontend/src/services/knowledgeService.ts:126` calls `POST /knowledge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/knowledge` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /phenomena (frontend/src/services/phenomenonService.ts:73)
`frontend/src/services/phenomenonService.ts:73` calls `POST /phenomena` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/phenomena` If this points at an external API, prefix it with `https://` so the matcher …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /projects (frontend/src/services/projectService.ts:111)
`frontend/src/services/projectService.ts:111` calls `POST /projects` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /projects/${id}/close-observation (frontend/src/services/projectService.ts:158)
`frontend/src/services/projectService.ts:158` calls `POST /projects/${id}/close-observation` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/close-observation` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /projects/${projectId}/ai/suggest-domain (frontend/src/services/aiService.ts:45)
`frontend/src/services/aiService.ts:45` calls `POST /projects/${projectId}/ai/suggest-domain` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/ai/suggest-domain` If this points at an external API…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /projects/${projectId}/ai/suggest-observations (frontend/src/services/aiService.ts:50)
`frontend/src/services/aiService.ts:50` calls `POST /projects/${projectId}/ai/suggest-observations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/ai/suggest-observations` If this points at an …
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: POST /projects/${projectId}/observations (frontend/src/services/observationService.ts:72)
`frontend/src/services/observationService.ts:72` calls `POST /projects/${projectId}/observations` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>/observations` If this points at an external API,…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /domains/${id} (frontend/src/services/domainService.ts:68)
`frontend/src/services/domainService.ts:68` calls `PUT /domains/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/domains/<p>` If this points at an external API, prefix it with `https://` so the matcher…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /observations/${id} (frontend/src/services/observationService.ts:84)
`frontend/src/services/observationService.ts:84` calls `PUT /observations/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/observations/<p>` If this points at an external API, prefix it with `https://`…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /phenomena/${id} (frontend/src/services/phenomenonService.ts:85)
`frontend/src/services/phenomenonService.ts:85` calls `PUT /phenomena/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/phenomena/<p>` 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: PUT /profile-permissions (frontend/src/services/governanceService.ts:26)
`frontend/src/services/governanceService.ts:26` calls `PUT /profile-permissions` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/profile-permissions` If this points at an external API, prefix it with `https:…
Dangling fetchHelper:request
high System graph api Wiring conf 1.00 Dangling fetch: PUT /projects/${id} (frontend/src/services/projectService.ts:120)
`frontend/src/services/projectService.ts:120` calls `PUT /projects/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/projects/<p>` 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: PUT /users/${id} (frontend/src/services/userService.ts:46)
`frontend/src/services/userService.ts:46` calls `PUT /users/${id}` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: helper:request Normalized path used for matching: `/users/<p>` If this points at an external API, prefix it with `https://` so the matcher skips…
Dangling fetchHelper:request
high System graph security auth conf 1.00 FastAPI DELETE `delete_attribute_override` without auth dependency — backend/v1/src/obione/visibility/router.py:44
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/v1/src/obione/visibility/router.py:44 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_project` without auth dependency — backend/v1/src/obione/projects/router.py:133
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/v1/src/obione/projects/router.py:133 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PATCH `update_project` without auth dependency — backend/v1/src/obione/projects/router.py:125
`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/v1/src/obione/projects/router.py:125 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `add_client` without auth dependency — backend/v1/src/obione/projects/router.py:138
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/v1/src/obione/projects/router.py:138 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_extraction` without auth dependency — backend/v1/src/obione/extractions/router.py:31
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/v1/src/obione/extractions/router.py:31 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_manual_extraction` without auth dependency — backend/v1/src/obione/extractions/router.py:100
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/v1/src/obione/extractions/router.py:100 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_project` without auth dependency — backend/v1/src/obione/projects/router.py:64
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/v1/src/obione/projects/router.py:64 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `submit_client` without auth dependency — backend/v1/src/obione/likert/router.py:27
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/v1/src/obione/likert/router.py:27 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `submit_consultoria` without auth dependency — backend/v1/src/obione/likert/router.py:19
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/v1/src/obione/likert/router.py:19 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `set_attribute` without auth dependency — backend/v1/src/obione/visibility/router.py:37
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/v1/src/obione/visibility/router.py:37 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `set_bulk` without auth dependency — backend/v1/src/obione/visibility/router.py:49
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/v1/src/obione/visibility/router.py:49 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `set_category` without auth dependency — backend/v1/src/obione/visibility/router.py:30
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
backend/v1/src/obione/visibility/router.py:30 securityAuth fastapi unauth mutation
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/components/ui/chart.tsx:73
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/v1/src/components/ui/chart.tsx:73
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/services/apiClient.ts:74
Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.
runtime safetyRobustness
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/settings.json
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/settings.json VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/apresentacao-poli/references/anti-patterns.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/apresentacao-poli/references/anti-patterns.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/apresentacao-poli/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/apresentacao-poli/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/documento-poli/SKILL.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
.claude/skills/documento-poli/SKILL.md VerificationClaude instruction
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
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 hardware Security conf 1.00 Dockerfile runs as root: backend/v1/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph hardware Security conf 1.00 Dockerfile runs as root: frontend/v1/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 Frontend route `/projects/:id/visibility` has no Link/navigate to it — frontend/v1/src/pages/ProjectVisibilityPage.test.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 Frontend route `/projects/:id` has no Link/navigate to it — frontend/v1/src/pages/ProjectDetailPage.test.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
Orphan pageWiring
medium System graph quality Integrity conf 1.00 Frontend route `/restricted` has no Link/navigate to it — frontend/v1/src/components/require-role.test.tsx
The route is registered but no `<Link to=…>` or `navigate(…)` in the codebase navigates here. Either it's reachable only via direct URL (intentional), it's dead, or the link broke during a refactor.
Orphan pageWiring
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/components/ui/chart.tsx:73
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/src/components/ui/chart.tsx:73 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/v1/src/components/ui/chart.tsx:73
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
frontend/v1/src/components/ui/chart.tsx:73 Dangerous innerhtml
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — .claude/skills/documento-poli/scripts/build_doc_pdf.py:47
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 135 placeholder/mock markers across 61 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 74 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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:22-alpine
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
frontend/v1/Dockerfile:1 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.11-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
backend/v1/Dockerfile:1 containersPinned dependencies
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: backend/v1/src/obione/synthesis/generator/port.py:synthesize, backend/v1/src/obione/extractions/llm/port.py:extract This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or docu…
duplicatesduplication
low System graph quality Integrity conf 1.00 19 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: backend/v1/src/obione/unit_of_work.py:commit, backend/v1/src/obione/unit_of_work.py:commit, backend/v1/src/obione/unit_of_work.py:commit This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene)…
19 occurrences
repo-level (19 hits)
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 `pagina_text_old` in .claude/skills/apresentacao-poli/scripts/build_status_report_template.py:160
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 `statusCodeToLegacy` in frontend/src/routes/domains.$id.tsx:54
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 `statusCodeToLegacy` in frontend/src/routes/index.tsx:18
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 `statusCodeToLegacy` in frontend/src/routes/projects.$id.tsx:136
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 `statusCodeToLegacy` in frontend/src/routes/projects.index.tsx:32
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: delete_shape_by_run_text
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/apresentacao-poli/scripts/pptx_helpers.py:161
low System graph software Dead code conf 1.00 13 occurrences Possibly dead Python function: downgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
12 files, 12 locations
backend/v1/alembic/versions/0001_create_users.py:50
backend/v1/alembic/versions/0002_create_projects.py:81
backend/v1/alembic/versions/0003_create_documents.py:57
backend/v1/alembic/versions/0005_create_comments.py:66
backend/v1/alembic/versions/0006_create_likert_responses.py:72
backend/v1/alembic/versions/0008_create_drafts.py:84
backend/v1/alembic/versions/0009_project_description_required.py:39
backend/v1/alembic/versions/0010_extractions_add_source_description_hash.py:32
low System graph software Dead code conf 1.00 Possibly dead Python function: highlight_runs
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/apresentacao-poli/scripts/pptx_helpers.py:218
low System graph software Dead code conf 1.00 Possibly dead Python function: reorder_slides
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
.claude/skills/apresentacao-poli/scripts/pptx_helpers.py:127
low System graph software Dead code conf 1.00 14 occurrences Possibly dead Python function: upgrade
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
12 files, 12 locations
backend/v1/alembic/versions/0001_create_users.py:20
backend/v1/alembic/versions/0002_create_projects.py:20
backend/v1/alembic/versions/0003_create_documents.py:20
backend/v1/alembic/versions/0005_create_comments.py:20
backend/v1/alembic/versions/0006_create_likert_responses.py:20
backend/v1/alembic/versions/0007_create_resumos.py:20
backend/v1/alembic/versions/0008_create_drafts.py:20
backend/v1/alembic/versions/0009_project_description_required.py:24
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 Integrity conf 1.00 Stub function `rollback` (body is just `pass`/`return`) — backend/v1/src/obione/unit_of_work.py:142
Likely an AI scaffold that was never filled in. Remove or implement.
Empty handlerDead code
low System graph api Wiring conf 1.00 Unused endpoint: DELETE /attributes/{attribute_key}
`backend/v1/src/obione/visibility/router.py` declares `DELETE /attributes/{attribute_key}` 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: DELETE /{comment_id}
`backend/v1/src/obione/comments/router.py` declares `DELETE /{comment_id}` 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: DELETE /{draft_id}
`backend/v1/src/obione/drafts/router.py` declares `DELETE /{draft_id}` 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: DELETE /{project_id}
`backend/v1/src/obione/projects/router.py` declares `DELETE /{project_id}` 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: DELETE /{synthesis_id}
`backend/v1/src/obione/synthesis/router.py` declares `DELETE /{synthesis_id}` 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: GET /
`backend/v1/src/obione/main.py` declares `GET /` 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: GET /cockpit
`backend/v1/src/obione/portfolio/router.py` declares `GET /cockpit` 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: GET /cockpit/themes/{domain}
`backend/v1/src/obione/portfolio/router.py` declares `GET /cockpit/themes/{domain}` 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: GET /coverage
`backend/v1/src/obione/extractions/router.py` declares `GET /coverage` 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: GET /coverage-matrix
`backend/v1/src/obione/portfolio/router.py` declares `GET /coverage-matrix` 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: GET /db
`backend/v1/src/obione/health/router.py` declares `GET /db` 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: GET /evaluation
`backend/v1/src/obione/extractions/router.py` declares `GET /evaluation` 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: GET /me
`backend/v1/src/obione/auth/router.py` declares `GET /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: GET /portfolio
`backend/v1/src/obione/projects/router.py` declares `GET /portfolio` 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: GET /responses
`backend/v1/src/obione/likert/router.py` declares `GET /responses` 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: GET /suggestions
`backend/v1/src/obione/themes/router.py` declares `GET /suggestions` 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: GET /summary
`backend/v1/src/obione/likert/router.py` declares `GET /summary` 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: GET /{draft_id}
`backend/v1/src/obione/drafts/router.py` declares `GET /{draft_id}` 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: GET /{project_id}
`backend/v1/src/obione/projects/router.py` declares `GET /{project_id}` 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: GET /{project_id}/detail
`backend/v1/src/obione/projects/router.py` declares `GET /{project_id}/detail` 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: GET /{synthesis_id}
`backend/v1/src/obione/synthesis/router.py` declares `GET /{synthesis_id}` 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: PATCH /{comment_id}
`backend/v1/src/obione/comments/router.py` declares `PATCH /{comment_id}` 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: PATCH /{draft_id}
`backend/v1/src/obione/drafts/router.py` declares `PATCH /{draft_id}` 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: PATCH /{project_id}
`backend/v1/src/obione/projects/router.py` declares `PATCH /{project_id}` 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: PATCH /{synthesis_id}
`backend/v1/src/obione/synthesis/router.py` declares `PATCH /{synthesis_id}` 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: POST /
`backend/v1/src/obione/projects/router.py` declares `POST /` 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: POST /client
`backend/v1/src/obione/likert/router.py` declares `POST /client` 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: POST /consultoria
`backend/v1/src/obione/likert/router.py` declares `POST /consultoria` 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: POST /generate
`backend/v1/src/obione/synthesis/router.py` declares `POST /generate` 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: POST /login
`backend/v1/src/obione/auth/router.py` declares `POST /login` 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: POST /manual
`backend/v1/src/obione/extractions/router.py` declares `POST /manual` 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: POST /suggest
`backend/v1/src/obione/themes/router.py` declares `POST /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: POST /suggestions/{suggestion_id}/accept
`backend/v1/src/obione/themes/router.py` declares `POST /suggestions/{suggestion_id}/accept` 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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /{draft_id}/publish
`backend/v1/src/obione/drafts/router.py` declares `POST /{draft_id}/publish` 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: POST /{project_id}/clients
`backend/v1/src/obione/projects/router.py` declares `POST /{project_id}/clients` 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: POST /{synthesis_id}/publish
`backend/v1/src/obione/synthesis/router.py` declares `POST /{synthesis_id}/publish` 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: PUT /
`backend/v1/src/obione/visibility/router.py` declares `PUT /` 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: PUT /attributes/{attribute_key}
`backend/v1/src/obione/visibility/router.py` declares `PUT /attributes/{attribute_key}` 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: PUT /categories/{category_key}
`backend/v1/src/obione/visibility/router.py` declares `PUT /categories/{category_key}` 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 cons…
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: frontend/src/routes/projects.$id.tsx (1929 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/3a8b8b90-561a-4b08-94db-9d2e88217c18/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/3a8b8b90-561a-4b08-94db-9d2e88217c18/

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.