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.

dare2live/lifehack

https://github.com/dare2live/lifehack · scanned 2026-06-17 01:53 UTC (1 month, 1 week ago)

193 raw signals (0 security + 193 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -3.7 (diff) · 175 actionable findings from 1 signal source. 18 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 175 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 33 Medium 30 Low 96 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 175 Crowd 0 Layer: Software 18 Security 32 Cicd 1 Quality 67 Api 57

Exclude dismissed / FP Exclude test files

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 6 places
low Near-duplicate function bodies in 3 places repo-level

View all duplicates & near-duplicates findings →

Legacy markers 2 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

2 matching findings on this repo

low Old/deprecated-named symbol `test_health_prefers_yearbook_over_legacy` in backe…
low Old/deprecated-named symbol `legacy_unused` in backend/scripts/migrate_register…

View all legacy markers findings →

Commented-out code 16 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/`.

12 matching findings on this repo

info Commented-code block (5 lines) in backend/tests/test_major_tags.py:148
info Commented-code block (5 lines) in backend/tests/test_phase0.py:65
info Commented-code block (9 lines) in backend/scripts/build_decision_tags.py:40
info Commented-code block (8 lines) in backend/services/major_city_employment_dispat…
info Commented-code block (5 lines) in backend/services/contract_recommend_vs_report…
info Commented-code block (5 lines) in backend/services/agent_workflow_task_results.…
info Commented-code block (5 lines) in backend/services/rank_destination.py:89
info Commented-code block (9 lines) in backend/services/recommendation/major_city_em…
info Commented-code block (7 lines) in frontend/js/tweaks-panel.js:12
info Commented-code block (5 lines) in frontend/js/modules/t_assembler.js:1
info Commented-code block (7 lines) in design/tweaks-panel.jsx:12
info Commented-code block (6 lines) in datahub/datahub/builders/outcome_policy_hint_…

View all commented-out code findings →

Config drift 9 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.

9 matching findings on this repo

low Possibly dead Python function: reload_configs backend/services/config_loader.py:137
medium Insecure pattern 'direct_innerhtml_assignment' in holland/frontend/js/survey_co… holland/frontend/js/survey_config.js:66
high FastAPI PATCH `patch_config` without auth dependency — backend/api/router_conso… backend/api/router_console.py:45
high Dangling fetch: GET /api/config/report_template (frontend/js/screens_reportpage…
high Dangling fetch: GET /api/config/decision_views (frontend/js/modules/decision_vi…
low Unused endpoint: GET /config
low Unused endpoint: GET /configs
low Unused endpoint: GET /config/{key}
low Unused endpoint: PATCH /config/{key}

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/cb7ebc15-b6e4-4b56-8615-0d3456c510b4/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/cb7ebc15-b6e4-4b56-8615-0d3456c510b4/

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.