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.

silviosotelo/esign-v3

https://github.com/silviosotelo/esign-v3 · scanned 2026-06-16 00:12 UTC (2 months, 2 weeks ago)

111 raw signals (3 security + 108 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 109 actionable findings from 2 signal sources. 2 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 · 106 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 2 Medium 9 Low 71 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 3 System graph 106 Crowd 0 Layer: Quality 24 Frontend 27 Network 1 Hardware 4 Security 3 Api 50

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.

Legacy markers 6 findings

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

6 matching findings on this repo

info TODO/FIXME marker in shipping code — backend/tests/integration/legacy.load.test…
low Stray `console.log` in TS/JS — backend/src/scripts/loadLegacy.js:115
low Stray `console.log` in TS/JS — backend/src/scripts/repairLegacyHashes.js:32
low Old/deprecated-named symbol `loadLegacy` in backend/tests/integration/legacy.lo…
low Old/deprecated-named symbol `loadLegacy` in backend/src/scripts/loadLegacy.js:6
info Commented-code block (7 lines) in backend/src/scripts/loadLegacy.js:214

View all legacy markers findings →

Commented-out code 8 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/`.

8 matching findings on this repo

info Commented-code block (5 lines) in frontend/src/components/fields/PdfFieldCanvas…
info Commented-code block (6 lines) in frontend/src/app/(dashboard)/contracts/[id]/f…
info Commented-code block (5 lines) in backend/src/api/v1/templates/index.js:44
info Commented-code block (5 lines) in backend/src/api/v1/branding/index.js:20
info Commented-code block (7 lines) in backend/src/scripts/loadLegacy.js:214
info Commented-code block (9 lines) in backend/src/database/migrations/005_signature…
info Commented-code block (7 lines) in backend/src/services/signature/signatureServi…
info Commented-code block (5 lines) in backend/src/services/identity/providers/tekoP…

View all commented-out code 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/a6d1da94-1daa-4552-9175-03956f92cc4e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/a6d1da94-1daa-4552-9175-03956f92cc4e/

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.