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.

robertoepifanio-byte/SHAREO

https://github.com/robertoepifanio-byte/SHAREO · scanned 2026-06-15 23:53 UTC (2 months, 3 weeks ago)

176 raw signals (32 security + 144 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 3 weeks ago · v1 · 145 actionable findings from 2 signal sources. 93 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 138 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 14 High 3 Medium 46 Low 52 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 7 System graph 138 Crowd 0 Layer: Quality 57 Security 21 Api 1 Frontend 63 Cicd 3

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Commented-out code 10 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

10 matching findings on this repo

info Commented-code block (5 lines) in jest.config.ts:47
info Commented-code block (7 lines) in middleware.ts:56
info Commented-code block (6 lines) in __tests__/integration/api/conversations/messa…
info Commented-code block (7 lines) in __tests__/unit/components/items/ItemCard.test…
info Commented-code block (5 lines) in scripts/create-admin-sessions.ts:103
info Commented-code block (5 lines) in e2e/security.spec.ts:146
info Commented-code block (5 lines) in e2e/booking-flow.spec.ts:285
info Commented-code block (5 lines) in e2e/e2e-a11y-plan.spec.ts:188
info Commented-code block (6 lines) in e2e/search-filter.spec.ts:3
info Commented-code block (9 lines) in e2e/error-pages.spec.ts:3

View all commented-out code findings →

Config drift 4 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

4 matching findings on this repo

high Agent instruction/config may expose a secret: CLAUDE.md CLAUDE.md:53
info Commented-code block (5 lines) in jest.config.ts:47
medium `fetch()` without try/.catch or AbortSignal — playwright.staging.config.ts:19
medium `fetch()` without try/.catch or AbortSignal — app/admin/embaixadores/_Ambassado…

View all config drift findings →

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/25b5216b-4553-4641-8801-17e42550caba/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/25b5216b-4553-4641-8801-17e42550caba/

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.