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.

R3n1er/e2ivoip-front

https://github.com/R3n1er/e2ivoip-front · scanned 2026-06-15 23:44 UTC (2 months, 4 weeks ago)

56 raw signals (0 security + 56 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 4 weeks ago · v1 · 56 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 56 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 1 Medium 20 Low 29 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 56 Crowd 0 Layer: Frontend 26 Security 9 Cicd 1 Quality 20

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 4 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.

4 matching findings on this repo

low Stray `console.log` in TS/JS — components/hubspot/legacy/hubspot-form-inline.ts…
low Stray `console.log` in TS/JS — components/hubspot/legacy/hubspot-forms.tsx:9
medium Insecure pattern 'direct_innerhtml_assignment' in components/hubspot/legacy/hub… components/hubspot/legacy/hubspot-form-inline.tsx:55
medium Insecure pattern 'direct_innerhtml_assignment' in components/hubspot/legacy/hub… components/hubspot/legacy/hubspot-form.tsx:47

View all legacy markers findings →

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

4 matching findings on this repo

info Commented-code block (6 lines) in tests/urlr.test.ts:201
info Commented-code block (6 lines) in tests/contact-page.test.tsx:13
info Commented-code block (5 lines) in tests/playwright/chat-animation-cycles.spec.t…
info Commented-code block (15 lines) in scripts/extract-blog-content.js:7

View all commented-out code findings →

Config drift 1 finding

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.

1 matching finding on this repo

high Agent instruction/config may expose a secret: .cursor/Next_js_Supabase_Auth_SSR… .cursor/Next_js_Supabase_Auth_SSR_Guidelines.mdc:71

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/1fd22a3d-3b30-419e-9223-4510b2507659/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/1fd22a3d-3b30-419e-9223-4510b2507659/

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.