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.
177 of your 267 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 72.95s for a 72.5 MB repo slow.
  • Repobility's analysis ran in 14.56s after the clone landed.

DashAISoftware/dashAI

https://github.com/DashAISoftware/dashAI · scanned 2026-06-05 17:15 UTC (4 days, 22 hours ago) · 10 languages

877 raw signals (253 security + 624 graph) 11/13 scanners ran 42nd percentile · Python · large (100-500K LoC)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 22 hours ago · v2 · 354 actionable findings from 2 signal sources. 192 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 51.0 0.20 10.20
documentation_score 70.0 0.15 10.50
practices_score 84.0 0.15 12.60
code_quality 58.0 0.10 5.80
Overall 1.00 73.1
security_score may be inflated — optional security scanners were skipped on this fast scan
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 7 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.
7 matching findings on this repo
  • low Near-duplicate function bodies in 9 places
  • low Near-duplicate function bodies in 2 places repo-level
  • low Near-duplicate function bodies in 7 places
  • low Near-duplicate function bodies in 4 places repo-level
  • low Near-duplicate function bodies in 3 places
  • low Near-duplicate function bodies in 6 places
  • low Near-duplicate function bodies in 5 places
View all duplicates & near-duplicates findings →
Commented-out code 8 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/`.
8 matching findings on this repo
  • info Commented-code block (5 lines) in tests/back/models/test_tabular_class_models.p…
  • info Commented-code block (7 lines) in tests/back/models/test_distilbert_transformer…
  • info Commented-code block (8 lines) in tests/back/dataloaders/test_dashai_dataset.py…
  • info Commented-code block (7 lines) in DashAI/front/src/utils/jobPoller.js:106
  • info Commented-code block (8 lines) in DashAI/front/src/utils/typesLists.js:15
  • info Commented-code block (5 lines) in DashAI/front/src/components/explorations/Step…
  • info Commented-code block (5 lines) in DashAI/front/src/hooks/useUpdateFlag.js:4
  • info Commented-code block (5 lines) in DashAI/back/dataloaders/classes/dashai_datase…
View all commented-out code findings →
Config drift 8 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.
8 matching findings on this repo
  • high [MINED131] pre-commit hook `https://github.com/pre-commit/pre-commit-hooks` pin… .pre-commit-config.yaml:2
  • low File has no detected symbols: docs/babel.config.js
  • low File has no detected symbols: docs/docusaurus.config.js
  • low File has no detected symbols: DashAI/front/i18next.config.js
  • low File has no detected symbols: DashAI/front/eslint.config.js
  • low File has no detected symbols: DashAI/front/src/types/configurableObject.ts
  • info TODO/FIXME marker in shipping code — DashAI/front/src/components/configurableOb…
  • info Commented-code block (5 lines) in DashAI/front/src/components/explorations/Step…
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/c45b5ec7-418d-40b0-b823-e292303fb389/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/c45b5ec7-418d-40b0-b823-e292303fb389/

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.