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.
Sign up free Scan another repo
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

gramps-project/gramps-web

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
Combined
60.3
/100
Security checks
54
88 findings
System graph
67
100.0% cov · 41 findings
Critical
4
click to filter
Agents
6
0 votes
Crowd
0
reported
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

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Possible secret in src/components/GrampsjsFormUser.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in src/components/GrampsjsFormUser.js:84; move to env var / secrets manager.
src/components/GrampsjsFormUser.js:84
#2
Possible secret in src/components/GrampsjsRelogin.js
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in src/components/GrampsjsRelogin.js:77; move to env var / secrets manager.
src/components/GrampsjsRelogin.js:77
#3
Docker base image uses a mutable or implicit tag: dmstraub/gramps-webapi:latest
GapSeverity.MEDIUM Layer.HARDWARE score 0.225
Why: medium severity
Dockerfile:1
#4
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/image-release.yml:23
#5
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/image-release.yml:26
#6
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/image-release.yml:34
#7
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/image-release.yml:47
#8
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/image-release.yml:58
#9
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/release.yml:28
#10
GitHub Action is tag-pinned rather than SHA-pinned
GapSeverity.MEDIUM Layer.CICD score 0.225
Why: medium severity
.github/workflows/image-devel.yml:23

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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.