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.

tipropark/faturamento

https://github.com/tipropark/faturamento · scanned 2026-06-16 00:37 UTC (2 months, 2 weeks ago)

714 raw signals (2 security + 712 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 414 Medium 103 Low 171 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 2 System graph 708 Crowd 0 Layer: Quality 128 Software 25 Frontend 127 Security 15 Cicd 1 Api 414

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.

Duplicates & near-duplicates 2 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

2 matching findings on this repo

low Near-duplicate function bodies in 2 places
low Near-duplicate function bodies in 6 places repo-level

View all duplicates & near-duplicates findings →

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

12 matching findings on this repo

info Commented-code block (6 lines) in public/sw.js:1
info Commented-code block (5 lines) in src/app/api/central-solicitacoes/[id]/route.t…
info Commented-code block (5 lines) in src/app/api/central-solicitacoes/[id]/aprovac…
info Commented-code block (5 lines) in src/app/api/mobile/v1/patio/app-config/route.…
info Commented-code block (5 lines) in src/app/api/admin/patio/resultados/route.ts:7
info Commented-code block (7 lines) in src/app/api/admin/patio/tickets/route.ts:7
info Commented-code block (6 lines) in src/app/api/admin/patio/caixas/route.ts:7
info Commented-code block (5 lines) in src/app/api/sac/mobichat/sync/route.ts:7
info Commented-code block (5 lines) in src/app/api/calendario/eventos/[id]/route.ts:9
info Commented-code block (7 lines) in src/lib/notifications/publisher.ts:8
info Commented-code block (5 lines) in src/lib/notifications/push-client.ts:1
info Commented-code block (5 lines) in src/lib/notifications/phone.ts:34

View all commented-out code findings →

Config drift 69 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.

12 matching findings on this repo

low Stray `console.log` in TS/JS — src/app/api/operacoes/[id]/agente-config/route.t…
medium `dangerouslySetInnerHTML` used in a React component — src/app/(dashboard)/centr…
medium `dangerouslySetInnerHTML` used in a React component — src/app/(dashboard)/centr…
medium Insecure pattern 'dangerous_innerhtml' in src/app/(dashboard)/central-solicitac… src/app/(dashboard)/central-solicitacoes/configur…:200
medium Insecure pattern 'dangerous_innerhtml' in src/app/(dashboard)/central-solicitac… src/app/(dashboard)/central-solicitacoes/configur…:329
high Agent instruction/config may expose a secret: skills/ai-studio-image/SKILL.md skills/ai-studio-image/SKILL.md:66
high Agent instruction/config may expose a secret: skills/antigravity-skill-orchestr… skills/antigravity-skill-orchestrator/SKILL.md:94
high Agent instruction/config may expose a secret: skills/n8n-mcp-tools-expert/SKILL… skills/n8n-mcp-tools-expert/SKILL.md:561
high Agent instruction/config may expose a secret: skills/devops-deploy/SKILL.md skills/devops-deploy/SKILL.md:101
low Old/deprecated-named symbol `try_backup` in skills/ai-studio-image/scripts/conf…
info Commented-code block (5 lines) in src/app/api/mobile/v1/patio/app-config/route.…
medium `fetch()` without try/.catch or AbortSignal — src/app/(dashboard)/central-solic…

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/e22310b1-dc8b-4b14-98c0-c37f81e97808/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e22310b1-dc8b-4b14-98c0-c37f81e97808/

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.