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.

TiveauHRTMN/weerzone.nl

https://github.com/TiveauHRTMN/weerzone.nl · scanned 2026-06-16 00:39 UTC (2 months, 1 week ago)

931 raw signals (9 security + 922 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

100.0% cov · 877 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 4 High 120 Medium 100 Low 381 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 5 System graph 877 Crowd 0 Layer: Quality 517 Software 22 Frontend 139 Hardware 3 Security 106 Cicd 3 Api 92

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 4 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.

4 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 3 places repo-level
low Near-duplicate function bodies in 4 places repo-level
low Near-duplicate function bodies in 5 places

View all duplicates & near-duplicates findings →

Legacy markers 9 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.

9 matching findings on this repo

low Old/deprecated-named symbol `get_legacy` in hermes-agent-main/tests/test_tui_ga…
low Old/deprecated-named symbol `user_legacy` in hermes-agent-main/tests/hermes_cli…
low Old/deprecated-named symbol `test_env_override_wins_over_legacy` in hermes-agen…
low Old/deprecated-named symbol `test_corrupt_owner_pid_falls_back_to_legacy` in he…
low Old/deprecated-named symbol `expected_legacy` in hermes-agent-main/tests/tools/…
low Old/deprecated-named symbol `test_text_as_dict_legacy` in hermes-agent-main/tes…
low Old/deprecated-named symbol `test_new_platforms_takes_precedence_over_legacy` i…
low Old/deprecated-named symbol `20Legacy` in hermes-agent-main/optional-skills/hea…
low Old/deprecated-named symbol `_warned_telegram_group_users_legacy` in hermes-age…

View all legacy markers findings →

Commented-out code 243 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 playwright.config.ts:74
info Commented-code block (6 lines) in temp_extract/design_handoff_weerzone_auth/twe…
info Commented-code block (6 lines) in temp_extract/design_handoff_weerzone_auth/des…
info Commented-code block (5 lines) in hermes-agent-main/hermes_state.py:167
info Commented-code block (6 lines) in hermes-agent-main/run_agent.py:45
info Commented-code block (5 lines) in hermes-agent-main/model_tools.py:110
info Commented-code block (5 lines) in hermes-agent-main/toolsets.py:363
info Commented-code block (6 lines) in hermes-agent-main/cli.py:397
info Commented-code block (5 lines) in hermes-agent-main/hermes_constants.py:48
info Commented-code block (7 lines) in hermes-agent-main/tests/conftest.py:264
info Commented-code block (5 lines) in hermes-agent-main/tests/test_tui_gateway_serv…
info Commented-code block (7 lines) in hermes-agent-main/tests/honcho_plugin/test_cl…

View all commented-out code findings →

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

12 matching findings on this repo

info `truncate` class without `title=` for hover reveal — hermes-agent-main/web/src/…
low Very large file: hermes-agent-main/hermes_cli/tools_config.py (2547 lines)
low Very large file: hermes-agent-main/hermes_cli/config.py (4837 lines)
low Very large file: hermes-agent-main/gateway/config.py (1625 lines)
medium Runtime service client appears to use placeholder configuration
high Agent instruction/config may expose a secret: hermes-agent-main/optional-skills… hermes-agent-main/optional-skills/security/sherlo…:101
high Agent instruction/config may expose a secret: hermes-agent-main/optional-skills… hermes-agent-main/optional-skills/email/agentmail…:44
high Agent instruction/config may expose a secret: hermes-agent-main/optional-skills… hermes-agent-main/optional-skills/mlops/chroma/SK…:90
high Agent instruction/config may expose a secret: hermes-agent-main/optional-skills… hermes-agent-main/optional-skills/mlops/hermes-at…:175
high Agent instruction/config may expose a secret: hermes-agent-main/optional-skills… hermes-agent-main/optional-skills/mlops/saelens/S…:87
high Agent instruction/config may expose a secret: hermes-agent-main/optional-skills… hermes-agent-main/optional-skills/mlops/simpo/SKI…:217
high Agent instruction/config may expose a secret: hermes-agent-main/optional-skills… hermes-agent-main/optional-skills/mlops/accelerat…:328

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/a255ea94-dd71-40c1-99f7-0ca7a1d171a0/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a255ea94-dd71-40c1-99f7-0ca7a1d171a0/

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.