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.

wagnerra23/oimpresso.com

https://github.com/wagnerra23/oimpresso.com · scanned 2026-06-16 00:55 UTC (2 months, 1 week ago)

1794 raw signals (0 security + 1794 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 1677 actionable findings from 1 signal source. 117 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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 5 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.
5 matching findings on this repo
  • low Near-duplicate function bodies in 3 places repo-level
  • low Near-duplicate function bodies in 2 places repo-level
  • low Near-duplicate function bodies in 4 places
  • low Near-duplicate function bodies in 6 places repo-level
  • low Near-duplicate function bodies in 9 places
View all duplicates & near-duplicates findings →
Legacy markers 29 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.
12 matching findings on this repo
  • low File has no detected symbols: scripts/fix_adr_legacy_schema.py
  • critical Possible secret in scripts/legacy-migration/migrar-martinho.py scripts/legacy-migration/migrar-martinho.py:48
  • critical Possible secret in scripts/legacy-migration/migrar-tudo.py scripts/legacy-migration/migrar-tudo.py:61
  • critical Possible secret in scripts/legacy-migration/daemon-sync-martinho.py scripts/legacy-migration/daemon-sync-martinho.py:97
  • critical Possible secret in scripts/legacy-migration/sql-wr2-pessoas/gerar-sql-cobrancas… scripts/legacy-migration/sql-wr2-pessoas/gerar-sq…:28
  • low Old/deprecated-named symbol `fromLegacy` in resources/js/Components/cockpit/Sid…
  • low Old/deprecated-named symbol `_KpiBarLegacy` in resources/js/Pages/Financeiro/Un…
  • low Old/deprecated-named symbol `cash_register_legacy` in resources/js/Pages/Financ…
  • low Old/deprecated-named symbol `toLegacy` in resources/plugins/fullcalendar/fullca…
  • low Old/deprecated-named symbol `toLegacy` in resources/plugins/fullcalendar/fullca…
  • low Old/deprecated-named symbol `toLegacy` in resources/plugins/fullcalendar/fullca…
  • low Old/deprecated-named symbol `delphi_legacy` in scripts/legacy-migration/import-…
View all legacy markers findings →
Commented-out code 434 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 (5 lines) in stylelint.config.mjs:3
  • info Commented-code block (7 lines) in vite.inertia.config.mjs:13
  • info Commented-code block (5 lines) in eslint.config.js:89
  • info Commented-code block (5 lines) in vitest.config.ts:4
  • info Commented-code block (6 lines) in tests/numberPtBR.test.ts:3
  • info Commented-code block (5 lines) in tests/product-keyboard-nav.test.tsx:3
  • info Commented-code block (5 lines) in tests/br-inputs.test.tsx:4
  • info Commented-code block (5 lines) in prototipo-ui/vendas-flow.jsx:171
  • info Commented-code block (8 lines) in prototipo-ui/vendas-page.jsx:65
  • info Commented-code block (7 lines) in prototipo-ui/integrity-check.mjs:8
  • info Commented-code block (8 lines) in prototipo-ui/ds-guard.mjs:8
  • info Commented-code block (5 lines) in prototipo-ui/data-vendas.jsx:314
View all commented-out code findings →
Config drift 21 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
  • info `truncate` class without `title=` for hover reveal — resources/js/Pages/Recurri…
  • info TODO/FIXME marker in shipping code — resources/js/Pages/Ponto/Configuracoes/Rep…
  • critical Possible secret in scripts/probe_configuracoes_grid_blob.py scripts/probe_configuracoes_grid_blob.py:77
  • critical Possible secret in scripts/probe_configuracoes_grid.py scripts/probe_configuracoes_grid.py:48
  • high Agent instruction/config may expose a secret: .claude/rules/reuse-check.md .claude/rules/reuse-check.md:38
  • high Agent instruction/config may expose a secret: .claude/commands/continuar.md .claude/commands/continuar.md:17
  • high Agent instruction/config may expose a secret: .claude/agents/como-integrar.md .claude/agents/como-integrar.md:49
  • high Agent instruction/config may expose a secret: .claude/skills/ads-decision-flow/… .claude/skills/ads-decision-flow/SKILL.md:172
  • high Agent instruction/config may expose a secret: .claude/skills/proxmox-docker-hos… .claude/skills/proxmox-docker-host/SKILL.md:56
  • high Agent instruction/config may expose a secret: .claude/skills/audit-constituicao… .claude/skills/audit-constituicao/SKILL.md:276
  • high Agent instruction/config may expose a secret: .claude/skills/audit-constituicao… .claude/skills/audit-constituicao/prompts/05-cycl…:12
  • high Agent instruction/config may expose a secret: .claude/skills/oimpresso-cc-watch… .claude/skills/oimpresso-cc-watcher-setup/SKILL.md:134
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/09f55eaf-1719-4109-95d0-b68110de4a48/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/09f55eaf-1719-4109-95d0-b68110de4a48/

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.