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.

abhmul/ask-chatgpt

https://github.com/abhmul/ask-chatgpt · scanned 2026-06-17 01:28 UTC (1 month, 2 weeks ago)

52 raw signals (0 security + 52 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ +18.5 (diff) · 44 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

44.4% cov · 44 findings

Severity distribution — click a segment to filter

Active filters: severity: medium × excluding tests × Reset all

Severity: Critical 0 High 0 Medium 2 Low 40 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 44 Crowd 0 Layer: Software 29 Quality 15

Exclude dismissed / FP Exclude test files

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Repository scanned at 95.2/100 with 44.4% coverage. It contains 1316 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 52 findings — concentrated in software (29), quality (23). Risk profile is low: 0 critical, 0 high, 2 medium. Recommended next step: open the software layer findings first — that's where the highest-impact wins live.

Showing 2 of 44 actionable findings. 52 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data

A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.

Mock dataCritical flowGenerated repo pattern

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 30 placeholder/mock markers across 8 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.

Mock dataIncompleteGenerated repo pattern

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/7419abfa-ce6e-4abb-9d2f-d389b8ed1258/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/7419abfa-ce6e-4abb-9d2f-d389b8ed1258/

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.