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.

dmmltda/gravity-antigravity

https://github.com/dmmltda/gravity-antigravity · scanned 2026-06-17 02:00 UTC (1 month, 1 week ago)

1376 raw signals (0 security + 1376 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v2 · last Δ -35.2 (diff) · 1226 actionable findings from 1 signal source. 150 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 1 finding
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.
1 matching finding on this repo
  • low Near-duplicate function bodies in 2 places
View all duplicates & near-duplicates findings →
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 — scripts/ativamente/migrate-legacy-test-ids.ts:143
  • low Old/deprecated-named symbol `hasLegacy` in scripts/sob-demanda/migrate-stripe-m…
  • low Old/deprecated-named symbol `idMatchLegacy` in scripts/ativamente/validate-test…
  • low Old/deprecated-named symbol `org_legacy` in testes/testes-funcionais/configurad…
View all legacy markers findings →
Commented-out code 172 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 (8 lines) in ecosystem.config.cjs:11
  • info Commented-code block (5 lines) in nucleo-global/Campos/campo-calendario-global/…
  • info Commented-code block (5 lines) in nucleo-global/Modais/modal-tabela-moeda/src/u…
  • info Commented-code block (5 lines) in nucleo-global/Modais/modal-tabela-unidades/sr…
  • info Commented-code block (5 lines) in nucleo-global/Tabelas/tabela-virtual-global/s…
  • info Commented-code block (6 lines) in nucleo-global/Tabelas/tabela-virtual-global/s…
  • info Commented-code block (5 lines) in nucleo-global/Tabelas/tabela-virtual-global/s…
  • info Commented-code block (6 lines) in nucleo-global/Tabelas/tabela-virtual-global/s…
  • info Commented-code block (5 lines) in nucleo-global/Tabelas/tabela-global/src/Tabel…
  • info Commented-code block (7 lines) in packages/resolver-organizacao/src/with-tenant…
  • info Commented-code block (5 lines) in packages/resolver-organizacao/src/middleware.…
  • info Commented-code block (9 lines) in scripts/gerar-mapa-enums-final.py:186
View all commented-out code findings →
Config drift 365 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 — configurador/generated/runtime/edge-esm.js:1
  • low Stray `console.log` in TS/JS — configurador/generated/runtime/react-native.js:2
  • low Stray `console.log` in TS/JS — configurador/generated/runtime/wasm.js:1
  • low Stray `console.log` in TS/JS — configurador/generated/runtime/edge.js:1
  • low Stray `console.log` in TS/JS — configurador/generated/runtime/library.js:3
  • info TODO/FIXME marker in shipping code — configurador/generated/runtime/library.d.t…
  • low Icon-only button without accessible name — servicos-global/configurador/src/pag…
  • info TODO/FIXME marker in shipping code — servicos-global/configurador/src/pages/adm…
  • info TODO/FIXME marker in shipping code — servicos-global/configurador/src/pages/con…
  • low Stray `console.log` in TS/JS — servicos-global/configurador/server/index.ts:612
  • low Stray `console.log` in TS/JS — servicos-global/configurador/server/workers/test…
  • low Stray `console.log` in TS/JS — servicos-global/configurador/server/scripts/list…
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/2a83e0b3-02a3-406c-a102-68c21d878334/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/2a83e0b3-02a3-406c-a102-68c21d878334/

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.