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.
Sign up free Scan another repo

Viniciusvile/Click-Prestare

https://github.com/Viniciusvile/Click-Prestare · scanned 2026-06-16 00:50 UTC (2 months, 1 week ago)

185 raw signals (0 security + 185 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
54.2
/100
Security checks
54
0 findings
System graph
54
100.0% cov · 184 findings
Critical
10
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 10 High 2 Medium 17 Low 138 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 184 Crowd 0 Layer: Software 1 Frontend 75 Network 1 Hardware 1 Security 20 Cicd 2 Quality 32 Api 52
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 54.2/100 with 100.0% coverage. It contains 1324 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 185 findings — concentrated in frontend (75), api (52), quality (32). Risk profile is high: 11 critical, 2 high, 17 medium. Recommended next step: open the frontend layer findings first — that's where the highest-impact wins live.

Showing 167 of 184 actionable findings. 185 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical System graph security Secrets conf 1.00 Possible secret in click-cond-api/click-cond-api/add_provider_app.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
click-cond-api/click-cond-api/add_provider_app.js:8
critical System graph security Secrets conf 1.00 Possible secret in click-cond-api/click-cond-api/add_visitor_app.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
click-cond-api/click-cond-api/add_visitor_app.js:8
critical System graph security Secrets conf 1.00 Possible secret in click-cond-api/click-cond-api/check_web_tables.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
click-cond-api/click-cond-api/check_web_tables.js:8
critical System graph security Secrets conf 1.00 Possible secret in click-cond-api/click-cond-api/create_sindico_railway.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
click-cond-api/click-cond-api/create_sindico_railway.js:8
critical System graph security Secrets conf 1.00 Possible secret in click-cond-api/click-cond-api/debug_mane.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
click-cond-api/click-cond-api/debug_mane.js:8
critical System graph security Secrets conf 1.00 Possible secret in click-cond-api/click-cond-api/populate_railway.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
click-cond-api/click-cond-api/populate_railway.js:8
critical System graph security Secrets conf 1.00 Possible secret in click-cond-api/click-cond-api/upgrade_financeiro.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
click-cond-api/click-cond-api/upgrade_financeiro.js:8
critical System graph security Secrets conf 1.00 Possible secret in click-cond-api/click-cond-api/verify_provider_sync.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
click-cond-api/click-cond-api/verify_provider_sync.js:8
critical System graph security Secrets conf 1.00 Possible secret in click-cond-api/click-cond-api/verify_sync.js
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
click-cond-api/click-cond-api/verify_sync.js:8
critical System graph security Secrets conf 1.00 2 occurrences Possible secret in click-cond-api/click-cond-api/views/userResetPassword.html
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
lines 26
click-cond-api/click-cond-api/views/userResetPassword.html:26 (2 hits)
high System graph api Wiring conf 1.00 Dangling fetch: GET /api (click-cond-web/apps/api-e2e/src/api/api.spec.ts:5)
`click-cond-web/apps/api-e2e/src/api/api.spec.ts:5` calls `GET /api` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: axios Normalized path used for matching: `/` If this points at an external API, prefix it with `https://` so the matcher skips it.
Dangling fetchAxios
high System graph api Wiring conf 1.00 Dangling fetch: POST https://api.openpix.com.br/v1/charge (click-cond-web/apps/api/src/app/financeiro/openpix.service.ts:17)
`click-cond-web/apps/api/src/app/financeiro/openpix.service.ts:17` calls `POST https://api.openpix.com.br/v1/charge` but no backend route matches that path. This is a runtime 404 waiting to happen. Tool: fetch Normalized path used for matching: `/https:/api.openpix.com.br/v1/charge` If this points…
Dangling fetchFetch
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: click-cond-web/.cursor/agents/ci-monitor-subagent.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
click-cond-web/.cursor/agents/ci-monitor-subagent.md VerificationCursor rule
medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: click-cond-web/.cursor/skills/nx-workspace/references/AFFECTED.md
This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.
click-cond-web/.cursor/skills/nx-workspace/references/AFFECTED.md VerificationCursor rule
medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing license, ci, lockfile. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci, lockfile. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in click-cond-api/click-cond-api/app.js:45
Found a known-risky pattern (cors_wildcard). Review and replace if possible.
click-cond-api/click-cond-api/app.js:45 Cors wildcard
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in click-cond-web/apps/api/src/assets/simulador-acesso.html:260
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
click-cond-web/apps/api/src/assets/simulador-acesso.html:260 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in click-cond-web/apps/api/src/assets/simulator.html:517
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
click-cond-web/apps/api/src/assets/simulator.html:517 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in click-cond-api/click-cond-api/create_final_user.js:22
Found a known-risky pattern (weak_hash). Review and replace if possible.
click-cond-api/click-cond-api/create_final_user.js:22 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in click-cond-api/click-cond-api/create_sindico_railway.js:28
Found a known-risky pattern (weak_hash). Review and replace if possible.
click-cond-api/click-cond-api/create_sindico_railway.js:28 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in click-cond-api/click-cond-api/create_user.js:24
Found a known-risky pattern (weak_hash). Review and replace if possible.
click-cond-api/click-cond-api/create_user.js:24 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in click-cond-api/click-cond-api/populate_railway.js:48
Found a known-risky pattern (weak_hash). Review and replace if possible.
click-cond-api/click-cond-api/populate_railway.js:48 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in click-cond-api/click-cond-api/src/database/DB_Funcionarios.js:11
Found a known-risky pattern (weak_hash). Review and replace if possible.
click-cond-api/click-cond-api/src/database/DB_Funcionarios.js:11 Weak hash
medium System graph security security conf 1.00 Insecure pattern 'weak_hash' in click-cond-api/click-cond-api/src/database/DB_Moradores.js:55
Found a known-risky pattern (weak_hash). Review and replace if possible.
click-cond-api/click-cond-api/src/database/DB_Moradores.js:55 Weak hash
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 18 placeholder/mock markers across 7 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
medium System graph network Security conf 1.00 Privileged port 465 in use
Port 465 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
click-cond-api/click-cond-api/src/services/Mails.js Ports
medium System graph quality Tests conf 1.00 Very low test-to-source ratio
8 test file(s) for 295 source file(s) (ratio 0.03). Consider adding integration or unit tests for critical paths.
Coverage
low System graph quality Integrity conf 1.00 25 env vars used in code but missing from .env.example
Drift between code and config docs. The first few: `ACCESS_COOLDOWN_MS`, `ANTI_PASSBACK_MODE`, `API_INTERNAL_URL`, `ASAAS_WEBHOOK_TOKEN`, `AUTH_FAILURE_WINDOW_MS`, `AUTH_LOCKOUT_MS`, `AUTH_MAX_FAILURES`, `AWS_S3_API_KEY` + 17 more. Add them (with a placeholder/comment) to .env.example so onboarding…
config drift
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 236 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph security security conf 1.00 Insecure pattern 'document_write' in click-cond-web/apps/portaria-web/src/app/encomendas/encomendas-page.component.ts:409
Found a known-risky pattern (document_write). Review and replace if possible.
click-cond-web/apps/portaria-web/src/app/encomendas/encomendas-page.component.ts:409 Document write
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality dependencies conf 1.00 Node manifest has dependencies but no lockfile: click-cond-web/apps/api/package.json
`package.json` declares dependencies, but no same-directory npm/pnpm/yarn/bun lockfile was found. Generated projects without lockfiles are less reproducible and harder to secure-scan precisely.
click-cond-web/apps/api/package.json LockfileReproducibilityGenerated repo pattern
low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
package.json CI/CD securitySupply chainNpm
low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts
preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.
click-cond-web/package.json CI/CD securitySupply chainNpm
low System graph software Dead code conf 1.00 Possibly dead Python function: handle_new_rx_page
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
click-cond-app/click-cond-app/ios/Flutter/ephemeral/flutter_lldb_helper.py:7
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/add_provider_app.js:17
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/add_visitor_app.js:17
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/check_all_condominios.js:14
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/check_apartment_users.js:17
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/check_columns.js:14
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/check_data.js:15
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/check_tables.js:14
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/check_users.js:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/check_web_tables.js:15
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/create_final_user.js:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/create_sindico_railway.js:18
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/create_user.js:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/debug_login.js:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/debug_mane.js:15
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/fix_user.js:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/get_morador.js:22
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/link_user.js:15
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/list_all_financeiro.js:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/list_condominios.js:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/migrate_codigo_acesso.js:13
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/migrate_visitantes.js:5
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/migrate_visitantes_direct.js:15
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/optimize_db.js:15
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/populate_railway.js:12
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/search_102.js:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/search_apto_debts.js:23
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/search_web_faturas.js:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/controller/ControllerAreasSociais.js:73
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/controller/ControllerFinanceiro.js:110
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/controller/ControllerMoradores.js:28
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/controller/ControllerMudancas.js:87
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/controller/ControllerOcorrencias.js:25
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/database/DB_Apartamento.js:25
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/database/DB_Assembleias.js:13
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/database/DB_Condominio.js:165
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/database/DB_Funcionarios.js:119
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/database/DB_Manutencoes.js:8
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/database/DB_Moradores.js:158
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/database/DB_Mudancas.js:37
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/database/DB_Ocorrencias.js:24
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/database/DB_Users.js:78
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/database/DB_Visitantes.js:23
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/database/MySQL.js:23
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/libs/fileStorage.js:39
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/libs/sequelize.js:16
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/middlewares/idValidator.js:8
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/middlewares/jwtVerify.js:11
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/middlewares/queryParamsValidator.js:7
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/middlewares/schemaValidator.js:7
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/services/Mails.js:34
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/services/Notifications.js:24
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/utils/logger.js:15
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/utils/saveToAWS.js:43
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/src/validations/getYupErrrors.js:4
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/test_inside.js:14
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/test_login.js:20
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/test_moradores_duplicados.js:13
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/test_ocorrencias.js:5
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/upgrade_financeiro.js:15
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/verify_provider_sync.js:14
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-api/click-cond-api/verify_sync.js:14
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-web/apps/api-e2e/src/support/global-setup.ts:8
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-web/apps/api-e2e/src/support/global-teardown.ts:9
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-web/apps/api/src/app/apartamentos/apartamentos.service.ts:167
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-web/apps/api/src/app/create_sindico.js:12
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-web/apps/api/src/app/moradores/moradores.service.ts:1148
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-web/apps/portaria-web/src/app/encomendas/encomendas-page.component.ts:680
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-web/prisma/seed.ts:17
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-web/prisma/stress_test.ts:71
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-web/scripts/clean-comunicados.ts:23
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-web/scripts/create-sindico.ts:41
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-web/scripts/criar-sindico-portaria.ts:8
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-web/scripts/seed-teste-banco.ts:114
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — click-cond-web/scripts/sync-moradores.ts:6
Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak
Fq console leak
low System graph api Wiring conf 1.00 Unused endpoint: GET /acessos/visitante/:id
`click-cond-api/click-cond-api/src/routes/facial.js` declares `GET /acessos/visitante/:id` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /condominios/get-all
`click-cond-api/click-cond-api/src/routes/dashboard.js` declares `GET /condominios/get-all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /get
`click-cond-api/click-cond-api/src/routes/mudancas.js` declares `GET /get` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /get-all
`click-cond-api/click-cond-api/src/routes/mudancas.js` declares `GET /get-all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /get-moradores
`click-cond-api/click-cond-api/src/routes/apartamentos.js` declares `GET /get-moradores` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /list-condominios
`click-cond-api/click-cond-api/src/routes/moradores.js` declares `GET /list-condominios` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /recovery/userResetPassword
`click-cond-api/click-cond-api/src/routes/utils.js` declares `GET /recovery/userResetPassword` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /summary
`click-cond-api/click-cond-api/src/routes/dashboard.js` declares `GET /summary` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /validar/:codigo
`click-cond-api/click-cond-api/src/routes/visitantes.js` declares `GET /validar/:codigo` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /votacoes/enquetes/get
`click-cond-api/click-cond-api/src/routes/assembleias.js` declares `GET /votacoes/enquetes/get` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /votacoes/enquetes/get-all
`click-cond-api/click-cond-api/src/routes/assembleias.js` declares `GET /votacoes/enquetes/get-all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documen…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /check-in
`click-cond-api/click-cond-api/src/routes/visitantes.js` declares `POST /check-in` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /check-out
`click-cond-api/click-cond-api/src/routes/visitantes.js` declares `POST /check-out` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consume…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /finish/insert
`click-cond-api/click-cond-api/src/routes/assembleias.js` declares `POST /finish/insert` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /insert
`click-cond-api/click-cond-api/src/routes/mudancas.js` declares `POST /insert` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /insert-familiar
`click-cond-api/click-cond-api/src/routes/moradores.js` declares `POST /insert-familiar` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /login
`click-cond-api/click-cond-api/src/routes/dashboard.js` declares `POST /login` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /new-password
`click-cond-api/click-cond-api/src/routes/moradores.js` declares `POST /new-password` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /recovery-password
`click-cond-api/click-cond-api/src/routes/moradores.js` declares `POST /recovery-password` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /recovery/userResetPassword
`click-cond-api/click-cond-api/src/routes/utils.js` declares `POST /recovery/userResetPassword` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /remove
`click-cond-api/click-cond-api/src/routes/mudancas.js` declares `POST /remove` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /retirar
`click-cond-api/click-cond-api/src/routes/encomendas.js` declares `POST /retirar` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /send-credentials
`click-cond-api/click-cond-api/src/routes/moradores.js` declares `POST /send-credentials` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who c…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /update
`click-cond-api/click-cond-api/src/routes/mudancas.js` declares `POST /update` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /update-assinatura
`click-cond-api/click-cond-api/src/routes/moradores.js` declares `POST /update-assinatura` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /update-status
`click-cond-api/click-cond-api/src/routes/mudancas.js` declares `POST /update-status` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consu…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /votacoes/finish
`click-cond-api/click-cond-api/src/routes/assembleias.js` declares `POST /votacoes/finish` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /votacoes/insert
`click-cond-api/click-cond-api/src/routes/assembleias.js` declares `POST /votacoes/insert` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /votacoes/remove
`click-cond-api/click-cond-api/src/routes/assembleias.js` declares `POST /votacoes/remove` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /votacoes/voto/insert
`click-cond-api/click-cond-api/src/routes/assembleias.js` declares `POST /votacoes/voto/insert` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /agenda
`click-cond-api/click-cond-api/app.js` declares `USE /agenda` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /apartamentos
`click-cond-api/click-cond-api/app.js` declares `USE /apartamentos` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /areas-sociais
`click-cond-api/click-cond-api/app.js` declares `USE /areas-sociais` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /assembleias
`click-cond-api/click-cond-api/app.js` declares `USE /assembleias` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /comunicados
`click-cond-api/click-cond-api/app.js` declares `USE /comunicados` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /condominio
`click-cond-api/click-cond-api/app.js` declares `USE /condominio` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /dashboard
`click-cond-api/click-cond-api/app.js` declares `USE /dashboard` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /documentos
`click-cond-api/click-cond-api/app.js` declares `USE /documentos` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /encomendas
`click-cond-api/click-cond-api/app.js` declares `USE /encomendas` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /facial
`click-cond-api/click-cond-api/app.js` declares `USE /facial` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /financeiro
`click-cond-api/click-cond-api/app.js` declares `USE /financeiro` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /funcionarios
`click-cond-api/click-cond-api/app.js` declares `USE /funcionarios` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /manutencoes
`click-cond-api/click-cond-api/app.js` declares `USE /manutencoes` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /moradores
`click-cond-api/click-cond-api/app.js` declares `USE /moradores` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /mudancas
`click-cond-api/click-cond-api/app.js` declares `USE /mudancas` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /ocorrencias
`click-cond-api/click-cond-api/app.js` declares `USE /ocorrencias` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /prestadores
`click-cond-api/click-cond-api/app.js` declares `USE /prestadores` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /sindico
`click-cond-api/click-cond-api/app.js` declares `USE /sindico` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /users
`click-cond-api/click-cond-api/app.js` declares `USE /users` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: USE /visitantes
`click-cond-api/click-cond-api/app.js` declares `USE /visitantes` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: click-cond-web/apps/api/src/app/auth/mobile-auth.service.ts (2216 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: click-cond-web/apps/api/src/app/facial/facial.service.ts (1471 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: click-cond-web/apps/api/src/app/financeiro/financeiro.service.ts (3062 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
low System graph quality Complexity conf 1.00 Very large file: click-cond-web/apps/api/src/app/visitantes/visitantes.service.ts (1478 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/d7ec0495-13c8-40fb-9e83-151484ef4f93/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/d7ec0495-13c8-40fb-9e83-151484ef4f93/

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.