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

dougsimpsoncodes/PinkAutoGlassWebsite

https://github.com/dougsimpsoncodes/PinkAutoGlassWebsite · scanned 2026-06-17 01:59 UTC (1 month, 1 week ago)

947 raw signals (0 security + 947 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -34.1 (diff) · 939 actionable findings from 1 signal source. 8 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
42.6
/100
Security checks
43
0 findings
System graph
43
100.0% cov · 939 findings
Critical
2
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 2 High 154 Medium 486 Low 261 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 939 Crowd 0 Layer: Frontend 447 Network 1 Security 218 Cicd 3 Quality 115 Api 155

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

#1
Possible secret in scripts/README.md
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 scripts/README.md:24; move to env var / secrets manager.
scripts/README.md:24
#2
Possible secret in security/baseline/gitleaks-historical-baseline.json
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 security/baseline/gitleaks-historical-baseline.json:797; move to env var / secrets manager.
security/baseline/gitleaks-historical-baseline.json:797
#3
Agent instruction/config may expose a secret: .claude/CLAUDE.md
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in .claude/CLAUDE.md:81; move to env var / secrets manager.
.claude/CLAUDE.md:81
#4
Agent instruction/config may expose a secret: .claude/skills/setup-satellite/SKILL.md
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in .claude/skills/setup-satellite/SKILL.md:160; move to env var / secrets manager.
.claude/skills/setup-satellite/SKILL.md:160
#5
`dangerouslySetInnerHTML` used in a React component — scripts/generate-locations.js:148
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#6
`dangerouslySetInnerHTML` used in a React component — scripts/generate-location-pages.js:103
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#7
`dangerouslySetInnerHTML` used in a React component — src/app/layout.tsx:115
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#8
`dangerouslySetInnerHTML` used in a React component — src/app/page.tsx:166
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#9
`dangerouslySetInnerHTML` used in a React component — src/app/locations/page.tsx:266
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#10
`dangerouslySetInnerHTML` used in a React component — src/app/locations/greeley-co/page.tsx:72
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity

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/c353d6ba-d50f-480b-83c6-b68d3a486832/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/c353d6ba-d50f-480b-83c6-b68d3a486832/

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.