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

dbreck/tablex-quoting-dashboard

https://github.com/dbreck/tablex-quoting-dashboard · scanned 2026-06-17 01:54 UTC (1 month, 1 week ago)

106 raw signals (0 security + 106 graph)

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

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -6.8 (diff) · 106 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
69.9
/100
Security checks
70
0 findings
System graph
70
88.9% cov · 106 findings
Critical
0
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 0 High 0 Medium 20 Low 30 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 106 Crowd 0 Layer: Api 1 Frontend 59 Security 8 Quality 38

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

#1
`dangerouslySetInnerHTML` used in a React component — src/app/(dashboard)/tablex-dna/TableXDnaClient.tsx:129
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#2
`dangerouslySetInnerHTML` used in a React component — src/components/content-map/ContentNodeDrawer.tsx:189
GapSeverity.MEDIUM Layer.FRONTEND score 0.360
Why: medium severity
#3
Insecure pattern 'node_child_process' in scripts/export-gf-quotes.ts:16
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
scripts/export-gf-quotes.ts:16
#4
Insecure pattern 'dangerous_innerhtml' in src/app/(dashboard)/tablex-dna/TableXDnaClient.tsx:129
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
src/app/(dashboard)/tablex-dna/TableXDnaClient.tsx:129
#5
Insecure pattern 'dangerous_innerhtml' in src/components/content-map/ContentNodeDrawer.tsx:189
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
src/components/content-map/ContentNodeDrawer.tsx:189
#6
Insecure pattern 'local_storage_auth_token' in src/components/comments/CommentInput.tsx:47
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
src/components/comments/CommentInput.tsx:47
#7
Insecure pattern 'direct_innerhtml_assignment' in public/wireframes/site.html:1355
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
public/wireframes/site.html:1355
#8
Insecure pattern 'direct_outerhtml_assignment' in public/wireframes/site.html:1409
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
public/wireframes/site.html:1409
#9
Insecure pattern 'direct_innerhtml_assignment' in public/wireframes/system.html:1830
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
public/wireframes/system.html:1830
#10
Insecure pattern 'direct_outerhtml_assignment' in public/wireframes/system.html:1884
GapSeverity.MEDIUM Layer.SECURITY score 0.248
Why: medium severity · OWASP-class risk
public/wireframes/system.html:1884

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/f93ac6c4-431a-4dea-8a1e-2a8d56170aad/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f93ac6c4-431a-4dea-8a1e-2a8d56170aad/

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.