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.

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)

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
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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

Duplicates & near-duplicates 3 findings
What it is: Same function copy-pasted into multiple modules with minor variations.
Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.
How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.
Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.
3 matching findings on this repo
  • low Near-duplicate function bodies in 2 places repo-level
  • low Near-duplicate function bodies in 4 places
  • low Near-duplicate function bodies in 3 places repo-level
View all duplicates & near-duplicates findings →
Commented-out code 9 findings
What it is: Lines of source that were intentionally disabled but never deleted.
Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.
How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.
Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.
9 matching findings on this repo
  • info Commented-code block (5 lines) in frontend/i18n.js:2529
  • info Commented-code block (5 lines) in tests/test_cr14_back_button.py:26
  • info Commented-code block (5 lines) in tests/test_seasonal_benchmark.py:19
  • info Commented-code block (6 lines) in design/mockups/insight-card/tweaks-panel.jsx:…
  • info Commented-code block (6 lines) in design/mockups/weekly-brief/tweaks-panel.jsx:…
  • info Commented-code block (6 lines) in web/public/mockups/insight-card/tweaks-panel.…
  • info Commented-code block (6 lines) in web/public/mockups/weekly-brief/tweaks-panel.…
  • info Commented-code block (6 lines) in src/cultivos/app.py:216
  • info Commented-code block (10 lines) in src/cultivos/api/__init__.py:90
View all commented-out code findings →
Config drift 6 findings
What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.
Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.
How AI causes it: AI writes new config from memory rather than reading the existing source.
Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.
6 matching findings on this repo
  • medium Runtime service client appears to use placeholder configuration
  • medium `fetch()` without try/.catch or AbortSignal — frontend/alert-config.js:137
  • high FastAPI POST `create_alert_config` without auth dependency — src/cultivos/api/a… src/cultivos/api/alert_config.py:45
  • high FastAPI PUT `update_alert_config` without auth dependency — src/cultivos/api/al… src/cultivos/api/alert_config.py:70
  • high Dangling fetch: PUT /api/farms/${farmId}/alert-config (frontend/alert-config.js…
  • low Unused endpoint: GET /alertas-config
View all config drift findings →
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/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.