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.

rogerlew/wepppy

https://github.com/rogerlew/wepppy · scanned 2026-06-15 23:57 UTC (2 months, 3 weeks ago)

712 raw signals (0 security + 712 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 616 actionable findings from 1 signal source. 96 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 · 616 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 4 High 106 Medium 233 Low 245 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 616 Crowd 0 Layer: Software 21 Frontend 24 Network 10 Hardware 13 Security 256 Cicd 2 Quality 232 Api 58

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 5 places
low Near-duplicate function bodies in 9 places

View all duplicates & near-duplicates findings →

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

12 matching findings on this repo

low Old/deprecated-named symbol `_PrepStubWithLegacy` in tests/rq/test_geneva_rq.py…
low Old/deprecated-named symbol `features_export_legacy` in tests/microservices/tes…
low Old/deprecated-named symbol `n_legacy` in tests/topo/test_watershed_abstraction…
low Old/deprecated-named symbol `_build_mofe_map_labels_python_legacy` in tests/nod…
low Old/deprecated-named symbol `test_export_input_legacy` in tests/nodb/mods/baer/…
low Old/deprecated-named symbol `a_lt_legacy` in docs/work-packages/20260522_ssurgo…
low Old/deprecated-named symbol `segmented_multiple_ofe_legacy` in wepppy/topo/wate…
low Old/deprecated-named symbol `has_legacy` in wepppy/topo/peridot/peridot_runner.…
low Old/deprecated-named symbol `fromLegacy` in wepppy/weppcloud/static/js/gl-dashb…
low Old/deprecated-named symbol `view_src_markdown_legacy` in wepppy/weppcloud/rout…
low Old/deprecated-named symbol `hintLegacy` in wepppy/weppcloud/controllers_js/gen…
low Old/deprecated-named symbol `legacy_v0_to_v1` in wepppy/nodb/mods/geneva/collab…

View all legacy markers findings →

Commented-out code 21 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 (8 lines) in tests/nodb/mods/baer/test_sbs_map_extended.py…
info Commented-code block (12 lines) in wepppy/eu/soils/esdac/esdac.py:127
info Commented-code block (12 lines) in wepppy/au/soils/soil_build.py:25
info Commented-code block (6 lines) in wepppy/soils/ssurgo/ssurgo.py:1512
info Commented-code block (5 lines) in wepppy/climates/downscaled_nmme_client.py:225
info Commented-code block (20 lines) in wepppy/climates/cligen/_scripts/stations_sql…
info Commented-code block (12 lines) in wepppy/locales/earth/soils/isric/__init__.py…
info Commented-code block (6 lines) in wepppy/wepp/management/managements.py:717
info Commented-code block (7 lines) in wepppy/wepp/interchange/watershed_chan_peak_i…
info Commented-code block (6 lines) in wepppy/all_your_base/geo/ogrmerge.py:20
info Commented-code block (8 lines) in wepppy/topo/topaz/topaz.py:558
info Commented-code block (8 lines) in wepppy/weppcloud/app.py:83

View all commented-out code findings →

Config drift 18 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

low Unused endpoint: POST /runs/{runid}/{config}/build-landuse
low Unused endpoint: POST /runs/{runid}/{config}/set-landuse-mode
low Unused endpoint: POST /runs/{runid}/{config}/set-landuse-db
low Unused endpoint: POST /runs/{runid}/{config}/modify-landuse-coverage
low Unused endpoint: GET /runs/{runid}/{config}/controllers/landuse/state
low Unused endpoint: POST /runs/{runid}/{config}/modify-landuse-mapping
low Unused endpoint: GET /runs/{runid}/{config}/landuse-user-defined/catalog
low Unused endpoint: POST /runs/{runid}/{config}/landuse-user-defined/upload
low Unused endpoint: POST /runs/{runid}/{config}/landuse-user-defined/delete
low Unused endpoint: POST /runs/{runid}/{config}/landuse-user-defined/update-descri…
low Unused endpoint: GET /runs/{runid}/{config}/landuse-map/snapshot
low Unused endpoint: POST /runs/{runid}/{config}/landuse-map/save

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/a3ccc34d-ef6c-42a8-803b-394265d76465/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a3ccc34d-ef6c-42a8-803b-394265d76465/

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.