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.

sanhvo86-hesem/mom

https://github.com/sanhvo86-hesem/mom · scanned 2026-06-16 00:05 UTC (2 months, 3 weeks ago)

591 raw signals (104 security + 487 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 455 actionable findings from 2 signal sources. 233 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 · 447 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 11 High 5 Medium 235 Low 172 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 8 System graph 447 Crowd 0 Layer: Quality 212 Security 169 Software 27 Frontend 37 Network 7 Hardware 1 Cicd 2

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 9 places

View all duplicates & near-duplicates findings →

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

10 matching findings on this repo

low Old/deprecated-named symbol `openDowntimeModalLegacy` in mom/scripts/portal/14-…
low Old/deprecated-named symbol `BrowserLegacy` in mom/scripts/portal/32-schema-stu…
low Old/deprecated-named symbol `renderSignatureBlockLegacy` in mom/scripts/portal/…
low Old/deprecated-named symbol `_applyLineSpacingLegacy` in mom/scripts/portal/03-…
low Old/deprecated-named symbol `loadDraftLegacy` in mom/scripts/portal/09b-form-fi…
low Old/deprecated-named symbol `machine_type_legacy` in mom/scripts/portal/13-mast…
low Old/deprecated-named symbol `_renderOnlineFormsLegacy` in mom/scripts/portal/09…
low Old/deprecated-named symbol `_fontSizeToLegacy` in mom/scripts/portal/06-tiptap…
low Old/deprecated-named symbol `matched_legacy` in mom/tools/registry/generate_wav…
low Old/deprecated-named symbol `archived_legacy` in mom/tools/contracts/generate_b…

View all legacy markers findings →

Commented-out code 30 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 tools/renumber_gates_8.py:310
info Commented-code block (6 lines) in tools/scripts/form-repair/unfreeze_and_audit.…
info Commented-code block (5 lines) in tools/scripts/translation/dcc_claude_cli_vi_t…
info Commented-code block (6 lines) in tools/scripts/translation/dcc_codex_cli_vi_to…
info Commented-code block (10 lines) in tools/scripts/translation/dcc_argos_vi_to_en…
info Commented-code block (6 lines) in tools/scripts/translation/dcc_nllb_vi_to_en.p…
info Commented-code block (7 lines) in mom/sw.js:24
info Commented-code block (6 lines) in mom/docs/forms/design-system/upgrade_frm641.p…
info Commented-code block (5 lines) in mom/scripts/portal/00c-admin-appearance-modul…
info Commented-code block (5 lines) in mom/scripts/portal/40-eqms-shell.js:2077
info Commented-code block (6 lines) in mom/scripts/portal/00d-admin-appearance-theme…
info Commented-code block (5 lines) in mom/scripts/portal/00j-admin-shared.js:495

View all commented-out code findings →

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

5 matching findings on this repo

low Stray `console.log` in TS/JS — mom/scripts/portal/01-data-config.js:274
medium Insecure pattern 'direct_innerhtml_assignment' in mom/scripts/portal/01-data-co… mom/scripts/portal/01-data-config.js:504
low Very large file: mom/scripts/portal/01-data-config.js (5448 lines)
info Commented-code block (5 lines) in mom/scripts/portal/01-data-config.js:156
medium `fetch()` without try/.catch or AbortSignal — mom/scripts/portal/01-data-config…

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/31c0cf45-25a4-4052-912f-f27074a3ba68/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/31c0cf45-25a4-4052-912f-f27074a3ba68/

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.