gramps-project/gramps-web

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.

18 of your 158 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 2.89s · analysis 50.98s · 5.6 MB · GitHub preflight 414ms

https://github.com/gramps-project/gramps-web · scanned 2026-06-05 13:15 UTC (5 days, 9 hours ago) · 10 languages

259 raw signals (153 security + 106 graph) 26th percentile · Javascript · medium (20-100K LoC) System graph score 67 (lower by 15)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 9 hours ago · v2 · 129 actionable findings from 2 signal sources. 77 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 · 41 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	100.0	0.15	15.00
`security_score`	9.0	0.25	2.25
`testing_score`	25.0	0.20	5.00
`documentation_score`	73.7	0.15	11.05
`practices_score`	85.0	0.15	12.75
`code_quality`	58.3	0.10	5.83
Overall		1.00	51.9

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 4 High 22 Medium 40 Low 42 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 88 System graph 41 Crowd 0 Layer: Quality 24 Security 10 Software 76 Cicd 6 Api 1 Frontend 7 Hardware 5

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.

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

3 matching findings on this repo

info Commented-code block (7 lines) in src/appState.js:31
info Commented-code block (6 lines) in src/components/styledTextPaste.js:34
info Commented-code block (11 lines) in src/components/GrampsjsEvents.js:114

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

medium npm package `eslint-config-prettier` is 3 major version(s) behind (7.2.0 -> 10.… package.json
low File has no detected symbols: rollup.config.js
low File has no detected symbols: vitest.config.js
low File has no detected symbols: src/config.js
low Stray `console.log` in TS/JS — rollup.config.js:23

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/e6b93f5d-3924-45dd-bc35-51f744a761fb/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e6b93f5d-3924-45dd-bc35-51f744a761fb/

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.