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.

vamseeachanta/digitalmodel

https://github.com/vamseeachanta/digitalmodel · scanned 2026-06-16 00:55 UTC (2 months, 1 week ago)

756 raw signals (0 security + 756 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 633 actionable findings from 1 signal source. 123 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 · 633 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 78 Medium 197 Low 220 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 633 Crowd 0 Layer: Software 31 Frontend 8 Network 43 Hardware 3 Security 79 Cicd 3 Quality 416 Api 50

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

View all duplicates & near-duplicates findings →

Legacy markers 55 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 Very large file: scripts/python/digitalmodel/legacy/generate_integration_charts…
low Very large file: scripts/python/digitalmodel/legacy/validate_phase2.py (1275 li…
low Very large file: .claude/_archive/claude-flow-era/commands/legacy-scripts/test-…
low Very large file: .claude/_archive/claude-flow-era/commands/legacy-scripts/test_…
low Very large file: .claude/_archive/claude-flow-era/commands/legacy-scripts/creat…
low Very large file: src/digitalmodel/subsea/catenary_riser/legacy/orcaflexModel.py…
high Agent instruction/config may expose a secret: .claude/_archive/claude-flow-era/… .claude/_archive/claude-flow-era/commands/legacy-…:84
medium Agent authority lacks a verifier contract: .claude/_archive/claude-flow-era/com… .claude/_archive/claude-flow-era/commands/legacy-…
low Old/deprecated-named symbol `test_hangoff_section_matches_legacy` in tests/test…
low Old/deprecated-named symbol `has_legacy` in tests/marine_ops/marine_engineering…
low Old/deprecated-named symbol `TestClassifyCardLegacy` in tests/marine_ops/artifi…
low Old/deprecated-named symbol `ref_wind_legacy` in tests/naming_convention_valida…

View all legacy markers findings →

Commented-out code 101 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 orcaflex_maturity_analysis.py:292
info Commented-code block (5 lines) in tests/test_wall_thickness_quickcheck_example.…
info Commented-code block (5 lines) in tests/test_attenuation_formula_check.py:72
info Commented-code block (5 lines) in tests/marine_ops/marine_engineering/visualiza…
info Commented-code block (5 lines) in tests/marine_ops/marine_engineering/catenary/…
info Commented-code block (5 lines) in tests/subsea/pipeline/test_api_rp_1111.py:63
info Commented-code block (5 lines) in tests/visualization/design_tools/pilot_progra…
info Commented-code block (5 lines) in tests/hydrodynamics/passing_ship/test_formula…
info Commented-code block (5 lines) in tests/hydrodynamics/passing_ship/test_wang_pa…
info Commented-code block (5 lines) in tests/solvers/orcaflex/modular_generator/test…
info Commented-code block (5 lines) in tests/solvers/orcaflex/modular_generator/inte…
info Commented-code block (6 lines) in tests/naval_architecture/test_yaw_moment_swee…

View all commented-out code findings →

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

medium Agent authority lacks a verifier contract: .claude/prompt_config.yaml .claude/prompt_config.yaml
high Agent instruction/config may expose a secret: .claude/_archive/claude-flow-era/… .claude/_archive/claude-flow-era/commands/github/…:68
high Agent instruction/config may expose a secret: .claude/_archive/claude-flow-era/… .claude/_archive/claude-flow-era/commands/github/…:78
high Agent instruction/config may expose a secret: .claude/_archive/claude-flow-era/… .claude/_archive/claude-flow-era/commands/github/…:227
high Agent instruction/config may expose a secret: .claude/_archive/claude-flow-era/… .claude/_archive/claude-flow-era/commands/github/…:228
high Agent instruction/config may expose a secret: .claude/_archive/claude-flow-era/… .claude/_archive/claude-flow-era/commands/github/…:92
high Agent instruction/config may expose a secret: .claude/_archive/claude-flow-era/… .claude/_archive/claude-flow-era/commands/hooks/p…:103
high Agent instruction/config may expose a secret: .claude/_archive/claude-flow-era/… .claude/_archive/claude-flow-era/commands/hooks/o…:77
high Agent instruction/config may expose a secret: .claude/_archive/claude-flow-era/… .claude/_archive/claude-flow-era/commands/flow-ne…:61
high Agent instruction/config may expose a secret: .claude/_archive/claude-flow-era/… .claude/_archive/claude-flow-era/commands/flow-ne…:136
high Agent instruction/config may expose a secret: .claude/_archive/claude-flow-era/… .claude/_archive/claude-flow-era/commands/legacy-…:84
high Agent instruction/config may expose a secret: .claude/_archive/claude-flow-era/… .claude/_archive/claude-flow-era/agents/AGENT-ARC…:162

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/a089203b-269f-4f3e-8382-b5cc5a9da0ff/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a089203b-269f-4f3e-8382-b5cc5a9da0ff/

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.