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.

abishek-oss/Gmail-dashboard

https://github.com/abishek-oss/Gmail-dashboard · scanned 2026-06-17 01:28 UTC (1 month, 2 weeks ago)

14 raw signals (0 security + 14 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

55.6% cov · 10 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 0 Medium 5 Low 3 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 10 Crowd 0 Layer: Frontend 1 Security 1 Cicd 2 Quality 6

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 55.5/100 with 55.6% coverage. It contains 62 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 14 findings — concentrated in cicd (6), quality (6), frontend (1). Risk profile is high: 1 critical, 0 high, 5 medium. Recommended next step: open the cicd layer findings first — that's where the highest-impact wins live.

Showing 9 of 10 actionable findings. 14 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.

critical System graph security Secrets conf 1.00 Possible secret in app/live.js

Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.

app/live.js:15

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — app/live.js:78

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Tests conf 1.00 CI is configured but no tests are detected

A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.

CI/CDConfig theaterRepo hardening

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 cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions

CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.

.github/workflows/jekyll-gh-pages.yml CI/CD securitySupply chainGithub actions

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

0 test file(s) for 5 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.

Coverage

low System graph quality Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: license, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.

Repo hardeningGenerated repo pattern

low System graph cicd CI/CD security conf 1.00 5 occurrences GitHub Action is tag-pinned rather than SHA-pinned

actions/checkout@v4 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.

lines 30, 32, 34, 39, 51

.github/workflows/jekyll-gh-pages.yml:30, 32, 34, 39, 51 (5 hits)

CI/CD securitySupply chainGithub actions

low System graph quality License conf 1.00 No license file detected

No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.

Repo hardeningGenerated 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/73fc5f87-91c5-4dd8-bf3f-7c343bae93f9/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/73fc5f87-91c5-4dd8-bf3f-7c343bae93f9/

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.