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

SebSanGar/cultivOS

https://github.com/SebSanGar/cultivOS · scanned 2026-06-16 00:06 UTC (2 months, 2 weeks ago)

251 raw signals (0 security + 251 graph)

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

Complete repo analysis

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

JSON
Combined
59.7
/100
Security checks
60
0 findings
System graph
60
100.0% cov · 244 findings
Critical
0
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 0 High 55 Medium 113 Low 65 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 244 Crowd 0 Layer: Software 1 Hardware 3 Security 125 Quality 52 Api 63
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 59.7/100 with 100.0% coverage. It contains 10259 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 251 findings — concentrated in security (125), api (63), quality (58). Risk profile is high: 0 critical, 55 high, 113 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 233 of 244 actionable findings. 251 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: GET /api/alerts/analytics (frontend/historial-alertas.js:169)
`frontend/historial-alertas.js:169` calls `GET /api/alerts/analytics` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/alerts/analytics` If this points at an external API, prefix it with `https://` so the matcher skip…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/alerts/history (frontend/historial-alertas.js:134)
`frontend/historial-alertas.js:134` calls `GET /api/alerts/history` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/alerts/history` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/cooperatives (frontend/ranking-miembros.js:13)
`frontend/ranking-miembros.js:13` calls `GET /api/cooperatives` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/cooperatives` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/farms/${selectedFarmId}/export?format=csv (frontend/app.js:1101)
`frontend/app.js:1101` calls `GET /api/farms/${selectedFarmId}/export?format=csv` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/farms/<p>/export` If this points at an external API, prefix it with `https://` so the …
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/intel/export (frontend/intel.js:737)
`frontend/intel.js:737` calls `GET /api/intel/export` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/intel/export` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/knowledge/crops (frontend/onboarding.js:19)
`frontend/onboarding.js:19` calls `GET /api/knowledge/crops` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/knowledge/crops` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: GET /api/system/health-detailed (frontend/api-status.js:8)
`frontend/api-status.js:8` calls `GET /api/system/health-detailed` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/system/health-detailed` If this points at an external API, prefix it with `https://` so the matcher s…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/farms/${farmId}/notifications/${notifId}/acknowledge (frontend/notifications.js:171)
`frontend/notifications.js:171` calls `POST /api/farms/${farmId}/notifications/${notifId}/acknowledge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/farms/<p>/notifications/<p>/acknowledge` If this points at an ext…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/farms/${selectedFarmId}/report (frontend/app.js:1130)
`frontend/app.js:1130` calls `POST /api/farms/${selectedFarmId}/report` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/farms/<p>/report` If this points at an external API, prefix it with `https://` so the matcher sk…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/intel/soil-amendment (frontend/calculadora-suelo.js:28)
`frontend/calculadora-suelo.js:28` calls `POST /api/intel/soil-amendment` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/intel/soil-amendment` If this points at an external API, prefix it with `https://` so the matc…
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/reports/portfolio (frontend/app.js:1156)
`frontend/app.js:1156` calls `POST /api/reports/portfolio` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/reports/portfolio` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: POST /api/reports/portfolio (frontend/reportes.js:59)
`frontend/reportes.js:59` calls `POST /api/reports/portfolio` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/reports/portfolio` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchFetch
high System graph api Wiring conf 1.00 Dangling fetch: PUT /api/farms/${farmId}/alert-config (frontend/alert-config.js:137)
`frontend/alert-config.js:137` calls `PUT /api/farms/${farmId}/alert-config` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/farms/<p>/alert-config` If this points at an external API, prefix it with `https://` so the…
Dangling fetchFetch
high System graph security auth conf 1.00 FastAPI DELETE `delete_cooperative` without auth dependency — src/cultivos/api/cooperatives.py:116
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/cooperatives.py:116 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_farm` without auth dependency — src/cultivos/api/farms.py:152
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/farms.py:152 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_field` without auth dependency — src/cultivos/api/farms.py:256
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/farms.py:256 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_photo` without auth dependency — src/cultivos/api/photos.py:75
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/photos.py:75 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI DELETE `delete_soil_analysis` without auth dependency — src/cultivos/api/soil.py:150
`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/soil.py:150 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `acknowledge_notification` without auth dependency — src/cultivos/api/notifications.py:55
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/notifications.py:55 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `analyze_ndvi` without auth dependency — src/cultivos/api/ndvi.py:29
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/ndvi.py:29 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `analyze_thermal` without auth dependency — src/cultivos/api/thermal.py:29
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/thermal.py:29 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `check_and_create_alerts` without auth dependency — src/cultivos/api/alerts.py:26
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/alerts.py:26 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `check_anomaly_alerts` without auth dependency — src/cultivos/api/alerts.py:205
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/alerts.py:205 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `check_irrigation_alerts` without auth dependency — src/cultivos/api/alerts.py:101
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/alerts.py:101 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `compute_field_health` without auth dependency — src/cultivos/api/health.py:28
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/health.py:28 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `compute_soil_amendment` without auth dependency — src/cultivos/api/soil_amendment.py:11
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/soil_amendment.py:11 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_alert_config` without auth dependency — src/cultivos/api/alert_config.py:45
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/alert_config.py:45 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_cooperative` without auth dependency — src/cultivos/api/cooperatives.py:68
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/cooperatives.py:68 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_field` without auth dependency — src/cultivos/api/farms.py:204
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/farms.py:204 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_harvest` without auth dependency — src/cultivos/api/harvests.py:85
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/harvests.py:85 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_microbiome_record` without auth dependency — src/cultivos/api/microbiome.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.
src/cultivos/api/microbiome.py:27 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_notification` without auth dependency — src/cultivos/api/notifications.py:20
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/notifications.py:20 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_observation` without auth dependency — src/cultivos/api/observations.py:40
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/observations.py:40 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_soil_analysis` without auth dependency — src/cultivos/api/soil.py:28
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/soil.py:28 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `create_weather_record` without auth dependency — src/cultivos/api/weather.py:25
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/weather.py:25 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `diagnose_problem` without auth dependency — src/cultivos/api/intel.py:446
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/intel.py:446 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `farmer_query` without auth dependency — src/cultivos/api/demo.py:83
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/demo.py:83 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `fertilizer_for_stress` without auth dependency — src/cultivos/api/intel.py:485
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/intel.py:485 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `generate_farm_report` without auth dependency — src/cultivos/api/reports.py:23
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/reports.py:23 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `generate_portfolio_report` without auth dependency — src/cultivos/api/portfolio_report.py:17
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/portfolio_report.py:17 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `generate_treatments` without auth dependency — src/cultivos/api/treatments.py:40
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/treatments.py:40 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `identify_disease` without auth dependency — src/cultivos/api/disease.py:36
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/disease.py:36 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `import_soil_csv` without auth dependency — src/cultivos/api/soil.py:44
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/soil.py:44 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `log_flight` without auth dependency — src/cultivos/api/flights.py:50
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/flights.py:50 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `log_treatment_applied` without auth dependency — src/cultivos/api/treatments.py:291
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/treatments.py:291 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `post_tek_adoption` without auth dependency — src/cultivos/api/tek_adoption.py:35
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/tek_adoption.py:35 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `record_carbon_baseline` without auth dependency — src/cultivos/api/farms.py:517
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/farms.py:517 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `sensor_fusion` without auth dependency — src/cultivos/api/fusion.py:62
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/fusion.py:62 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `submit_feedback` without auth dependency — src/cultivos/api/feedback.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.
src/cultivos/api/feedback.py:27 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI POST `upload_photo` without auth dependency — src/cultivos/api/photos.py:25
`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/photos.py:25 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_alert_config` without auth dependency — src/cultivos/api/alert_config.py:70
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/alert_config.py:70 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_cooperative` without auth dependency — src/cultivos/api/cooperatives.py:103
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/cooperatives.py:103 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_farm` without auth dependency — src/cultivos/api/farms.py:139
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/farms.py:139 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_field` without auth dependency — src/cultivos/api/farms.py:239
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/farms.py:239 securityAuth fastapi unauth mutation
high System graph security auth conf 1.00 FastAPI PUT `update_soil_analysis` without auth dependency — src/cultivos/api/soil.py:126
`@router.put` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.
src/cultivos/api/soil.py:126 securityAuth fastapi unauth mutation
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/alert-config.js:137
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/alineacion-tek.js:15
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/app.js:588
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/calendario-campo.js:24
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/calendario.js:8
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/cerebro-analytics.js:7
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/cooperativa.js:7
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/efectividad-intervenciones.js:7
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/ejecutivo.js:7
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/escalaciones-alertas.js:11
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/exportar.js:96
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/field.js:2158
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/fotos.js:16
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/frescura-sensores.js:9
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/indice-estres.js:20
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/intel.js:737
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/knowledge.js:56
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/login.js:117
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/management.js:35
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/onboarding.js:203
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/plan-accion.js:12
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/precision-ia.js:7
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/prediccion-salud.js:14
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/prioridad-riesgo.js:11
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/reporte-anual.js:24
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/trayectoria.js:9
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 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: Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/actions.js:90
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/actions.js:90 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/alertas-clima.js:46
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/alertas-clima.js:46 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/alertas-estacionales.js:50
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/alertas-estacionales.js:50 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/alineacion-tek.js:24
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/alineacion-tek.js:24 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/anomalies.js:42
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/anomalies.js:42 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/api-docs.js:55
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/api-docs.js:55 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/app.js:125
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/app.js:125 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/auth-guard.js:38
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/auth-guard.js:38 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/calculadora-suelo.js:51
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/calculadora-suelo.js:51 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/calendario-campo.js:20
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/calendario-campo.js:20 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/calendario.js:38
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/calendario.js:38 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/carbon.js:41
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/carbon.js:41 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/cerebro-analytics.js:111
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/cerebro-analytics.js:111 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/clima.js:76
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/clima.js:76 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/comparar.js:111
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/comparar.js:111 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/completitud-global.js:79
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/completitud-global.js:79 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/completitud.js:53
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/completitud.js:53 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/confianza-tratamientos.js:76
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/confianza-tratamientos.js:76 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/coop-evidencia.js:52
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/coop-evidencia.js:52 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/coop-progreso-mensual.js:91
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/coop-progreso-mensual.js:91 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/cooperativa.js:26
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/cooperativa.js:26 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/correlacion-ndvi.js:22
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/correlacion-ndvi.js:22 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/demo-fodecijal.js:47
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/demo-fodecijal.js:47 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/disease.js:67
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/disease.js:67 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/diversidad-cultivos.js:96
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/diversidad-cultivos.js:96 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/economic-impact.js:465
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/economic-impact.js:465 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/efectividad-global.js:173
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/efectividad-global.js:173 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/efectividad-intervenciones.js:25
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/efectividad-intervenciones.js:25 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/efectividad.js:35
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/efectividad.js:35 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/ejecutivo.js:96
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/ejecutivo.js:96 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/escalaciones-alertas.js:54
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/escalaciones-alertas.js:54 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/exportar.js:38
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/exportar.js:38 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/field.js:466
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/field.js:466 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/flights.js:54
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/flights.js:54 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/fotos.js:38
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/fotos.js:38 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/frescura-sensores.js:27
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/frescura-sensores.js:27 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/fusion-page.js:45
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/fusion-page.js:45 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/historial-alertas.js:87
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/historial-alertas.js:87 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/historial-enfermedades.js:75
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/historial-enfermedades.js:75 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/hitos-regenerativos.js:36
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/hitos-regenerativos.js:36 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/impacto-agricultor.js:41
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/impacto-agricultor.js:41 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/indice-estres.js:92
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/indice-estres.js:92 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/intel.js:64
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/intel.js:64 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/intelligence-page.js:54
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/intelligence-page.js:54 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/intervenciones.js:31
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/intervenciones.js:31 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/irrigation.js:60
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/irrigation.js:60 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/knowledge.js:66
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/knowledge.js:66 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/management.js:52
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/management.js:52 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/mapa.js:291
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/mapa.js:291 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/microbiome.js:57
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/microbiome.js:57 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/mission.js:48
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/mission.js:48 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/notifications.js:47
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/notifications.js:47 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/nutrientes-suelo.js:80
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/nutrientes-suelo.js:80 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/onboarding.js:94
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/onboarding.js:94 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/plan-accion.js:30
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/plan-accion.js:30 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/precision-ia.js:79
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/precision-ia.js:79 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/prediccion-salud.js:79
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/prediccion-salud.js:79 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/prioridad-riesgo.js:23
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/prioridad-riesgo.js:23 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/ranking-miembros.js:29
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/ranking-miembros.js:29 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/recommendations.js:72
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/recommendations.js:72 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/regenerative.js:39
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/regenerative.js:39 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/regional.js:76
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/regional.js:76 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/reporte-anual.js:52
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/reporte-anual.js:52 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/reportes.js:19
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/reportes.js:19 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/resiliencia.js:60
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/resiliencia.js:60 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/resumen.js:111
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/resumen.js:111 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/roi-tratamientos.js:62
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/roi-tratamientos.js:62 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/rotation.js:61
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/rotation.js:61 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/seasonal.js:49
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/seasonal.js:49 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/soil-history.js:77
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/soil-history.js:77 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/soil-import.js:35
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/soil-import.js:35 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/status.js:104
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/status.js:104 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/tek-page.js:28
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/tek-page.js:28 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/thermal-dashboard.js:76
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/thermal-dashboard.js:76 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/timeline.js:80
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/timeline.js:80 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/tour.js:222
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/tour.js:222 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/trayectoria.js:31
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/trayectoria.js:31 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/walkthrough.html:252
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/walkthrough.html:252 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/whatsapp-demo.js:72
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/whatsapp-demo.js:72 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/yield.js:55
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
frontend/yield.js:55 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in index.html:1198
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
index.html:1198 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'insert_adjacent_html' in frontend/intel.js:657
Found a known-risky pattern (insert_adjacent_html). Review and replace if possible.
frontend/intel.js:657 Insert adjacent html
medium System graph security security conf 1.00 Insecure pattern 'local_storage_auth_token' in frontend/login.js:147
Found a known-risky pattern (local_storage_auth_token). Review and replace if possible.
frontend/login.js:147 Local storage auth token
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 55 placeholder/mock markers across 11 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Runtime service client appears to use placeholder configuration
A runtime source file appears to wire Supabase/Firebase/AI/payment-style clients to placeholder URLs, keys, or fallback values. In the Fable corpus this often means the UI/API shape is present while the backend service is not actually configured.
Runtime configService clientGenerated 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 11 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 2 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
lines 2, 9
Dockerfile:2, 9 (2 hits)
containersPinned dependencies
low System graph quality Integrity conf 1.00 6 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: src/cultivos/app.py:dispatch, src/cultivos/app.py:dispatch This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
6 occurrences
repo-level (6 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 2 occurrences Near-duplicate function bodies in 3 places
Functions with the same first-5-line body hash: src/cultivos/api/farm_digest.py:get_farm_digest, src/cultivos/api/irrigation_efficiency.py:get_farm_irrigation_efficiency, src/cultivos/api/farm_saludo_diario.py:get_saludo_diario This is *the* AI-coder failure mode (4× more duplication in vibe-coded…
2 occurrences
repo-level (2 hits)
duplicatesduplication
low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 4 places
Functions with the same first-5-line body hash: src/cultivos/api/field_alertas_criticas.py:get_alertas_criticas, src/cultivos/api/field_accion.py:get_field_accion_siguiente, src/cultivos/api/field_resumen.py:get_field_resumen, src/cultivos/api/field_trayectoria.py:get_field_trayectoria_semana This…
duplicatesduplication
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `hs_old` in tests/test_dashboard.py:25
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 `test_no_currency_code_in_user_copy` in tests/test_nb_fs_farmer_savings.py:37
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: require_farm_access
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
src/cultivos/auth.py:124
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 api Wiring conf 1.00 Unused endpoint: GET /
`src/cultivos/app.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 /acciones
`src/cultivos/app.py` declares `GET /acciones` 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 /alertas-config
`src/cultivos/app.py` declares `GET /alertas-config` 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 /alertas-estacionales
`src/cultivos/app.py` declares `GET /alertas-estacionales` 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 /anomalias
`src/cultivos/app.py` declares `GET /anomalias` 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 /api/health
`src/cultivos/app.py` declares `GET /api/health` 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 /api/readiness
`src/cultivos/app.py` declares `GET /api/readiness` 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 /api/sentry-debug
`src/cultivos/app.py` declares `GET /api/sentry-debug` 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 /calendario
`src/cultivos/app.py` declares `GET /calendario` 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 /campo
`src/cultivos/app.py` declares `GET /campo` 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 /carbono
`src/cultivos/app.py` declares `GET /carbono` 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 /clima
`src/cultivos/app.py` declares `GET /clima` 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 /comparar
`src/cultivos/app.py` declares `GET /comparar` 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 /completitud
`src/cultivos/app.py` declares `GET /completitud` 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 /completitud-global
`src/cultivos/app.py` declares `GET /completitud-global` 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 /conocimiento
`src/cultivos/app.py` declares `GET /conocimiento` 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 /demo
`src/cultivos/app.py` declares `GET /demo` 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 /docs-api
`src/cultivos/app.py` declares `GET /docs-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: GET /efectividad
`src/cultivos/app.py` declares `GET /efectividad` 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 /efectividad-global
`src/cultivos/app.py` declares `GET /efectividad-global` 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 /enfermedades
`src/cultivos/app.py` declares `GET /enfermedades` 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 /estaciones
`src/cultivos/app.py` declares `GET /estaciones` 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 /estado
`src/cultivos/app.py` declares `GET /estado` 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 /exportar
`src/cultivos/app.py` declares `GET /exportar` 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 /fusion
`src/cultivos/app.py` declares `GET /fusion` 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 /gestion
`src/cultivos/app.py` declares `GET /gestion` 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 /historial
`src/cultivos/app.py` declares `GET /historial` 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 /impacto-economico
`src/cultivos/app.py` declares `GET /impacto-economico` 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 /importar-suelo
`src/cultivos/app.py` declares `GET /importar-suelo` 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 /intel
`src/cultivos/app.py` declares `GET /intel` 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 /inteligencia
`src/cultivos/app.py` declares `GET /inteligencia` 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 /intervenciones
`src/cultivos/app.py` declares `GET /intervenciones` 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 /login
`src/cultivos/app.py` declares `GET /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: GET /mapa
`src/cultivos/app.py` declares `GET /mapa` 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 /microbioma
`src/cultivos/app.py` declares `GET /microbioma` 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 /mision
`src/cultivos/app.py` declares `GET /mision` 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 /notificaciones
`src/cultivos/app.py` declares `GET /notificaciones` 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 /onboarding
`src/cultivos/app.py` declares `GET /onboarding` 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 /recomendaciones
`src/cultivos/app.py` declares `GET /recomendaciones` 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 /recorrido
`src/cultivos/app.py` declares `GET /recorrido` 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 /regenerativo
`src/cultivos/app.py` declares `GET /regenerativo` 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 /regional
`src/cultivos/app.py` declares `GET /regional` 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 /rendimiento
`src/cultivos/app.py` declares `GET /rendimiento` 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 /reportes
`src/cultivos/app.py` declares `GET /reportes` 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 /riego
`src/cultivos/app.py` declares `GET /riego` 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 /rotacion
`src/cultivos/app.py` declares `GET /rotacion` 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 /suelo
`src/cultivos/app.py` declares `GET /suelo` 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 /tek
`src/cultivos/app.py` declares `GET /tek` 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 /termica
`src/cultivos/app.py` declares `GET /termica` 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 /vuelos
`src/cultivos/app.py` declares `GET /vuelos` 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 quality Complexity conf 1.00 Very large file: frontend/app.js (1309 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/field.js (2450 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: frontend/i18n.js (2602 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/cultivos/db/seeds.py (1665 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: src/cultivos/services/intelligence/analytics.py (1815 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/00204165-600a-4942-b9bc-2c8a8ffb78b1/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/00204165-600a-4942-b9bc-2c8a8ffb78b1/

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.