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.

nomad3/booking-system-aremko

https://github.com/nomad3/booking-system-aremko · scanned 2026-06-16 04:35 UTC (1 month, 3 weeks ago)

48 raw signals (0 security + 48 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

77.8% cov · 46 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 3 Medium 27 Low 12 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 46 Crowd 0 Layer: Software 4 Api 1 Hardware 2 Security 6 Quality 33

Exclude dismissed / FP Exclude test files

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 64.0/100 with 77.8% coverage. It contains 407 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 48 findings — concentrated in quality (35), security (6), software (4). Risk profile is high: 2 critical, 3 high, 27 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 44 of 46 actionable findings. 48 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 .env.backup.example

Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.

.env.backup.example:38

critical System graph security Secrets conf 1.00 Possible secret in import_clientes_standalone.py

Detected pattern matching password_literal. Rotate the credential and move to a secret manager.

import_clientes_standalone.py:67

high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: CLAUDE.md

Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.

CLAUDE.md:193 SecretsClaude instruction

high System graph security security conf 1.00 Insecure pattern 'exec_used' in encontrar_error_admin.py:32

Found a known-risky pattern (exec_used). Review and replace if possible.

encontrar_error_admin.py:32 Exec used

high System graph security security conf 1.00 Insecure pattern 'exec_used' in fix_serviciobloqueo_completo.py:86

Found a known-risky pattern (exec_used). Review and replace if possible.

fix_serviciobloqueo_completo.py:86 Exec used

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. 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 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 hardware Security conf 1.00 Dockerfile runs as root: Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

Container

medium System graph quality Integrity conf 1.00 Likely N+1 query: `for c in …` triggers a query per row — diagnosticar_comandas.py:74

The loop iterates a Django queryset and accesses `c.detalles.count` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 queries ins…

diagnosticar_comandas.py:74 N plus onePerformance

medium System graph quality Integrity conf 1.00 Likely N+1 query: `for cliente in …` triggers a query per row — analyze_remaining_duplicates.py:29

The loop iterates a Django queryset and accesses `cliente.telefono.replace` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 que…

analyze_remaining_duplicates.py:29 N plus onePerformance

medium System graph quality Integrity conf 1.00 Likely N+1 query: `for cliente in …` triggers a query per row — fix_all_duplicates.py:31

fix_all_duplicates.py:31 N plus onePerformance

medium System graph quality Integrity conf 1.00 Likely N+1 query: `for cliente in …` triggers a query per row — merge_historical_to_current.py:208

merge_historical_to_current.py:208 N plus onePerformance

medium System graph quality Integrity conf 1.00 Likely N+1 query: `for detalle in …` triggers a query per row — capturar_error_comanda.py:189

The loop iterates a Django queryset and accesses `detalle.producto.nombre` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 quer…

capturar_error_comanda.py:189 N plus onePerformance

medium System graph quality Integrity conf 1.00 Likely N+1 query: `for detalle in …` triggers a query per row — fix_comanda_validacion_estricta.py:143

fix_comanda_validacion_estricta.py:143 N plus onePerformance

medium System graph quality Integrity conf 1.00 Likely N+1 query: `for detalle in …` triggers a query per row — revertir_admin_comanda.py:72

The loop iterates a Django queryset and accesses `detalle.producto.cantidad_disponible` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everythin…

revertir_admin_comanda.py:72 N plus onePerformance

medium System graph quality Integrity conf 1.00 Likely N+1 query: `for instance in …` triggers a query per row — revertir_admin_comanda.py:33

The loop iterates a Django queryset and accesses `instance.producto.cantidad_disponible` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everythi…

revertir_admin_comanda.py:33 N plus onePerformance

medium System graph quality Integrity conf 1.00 Likely N+1 query: `for p in …` triggers a query per row — diagnose_agenda.py:173

The loop iterates a Django queryset and accesses `p.producto.nombre` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 queries in…

diagnose_agenda.py:173 N plus onePerformance

medium System graph quality Integrity conf 1.00 Likely N+1 query: `for pago in …` triggers a query per row — diagnostico_giftcards.py:65

The loop iterates a Django queryset and accesses `pago.giftcard.codigo` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 queries…

diagnostico_giftcards.py:65 N plus onePerformance

medium System graph quality Integrity conf 1.00 Likely N+1 query: `for producto in …` triggers a query per row — diagnose_agenda.py:118

The loop iterates a Django queryset and accesses `producto.producto.nombre` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 que…

diagnose_agenda.py:118 N plus onePerformance

medium System graph quality Integrity conf 1.00 Likely N+1 query: `for producto in …` triggers a query per row — diagnose_agenda.py:155

diagnose_agenda.py:155 N plus onePerformance

medium System graph quality Integrity conf 1.00 Likely N+1 query: `for r in …` triggers a query per row — diagnosticar_comandas.py:60

The loop iterates a Django queryset and accesses `r.cliente.nombre` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 queries ins…

diagnosticar_comandas.py:60 N plus onePerformance

medium System graph quality Integrity conf 1.00 Likely N+1 query: `for rs in …` triggers a query per row — diagnostico_gastos.py:57

The loop iterates a Django queryset and accesses `rs.venta_reserva.fecha_reserva` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1…

diagnostico_gastos.py:57 N plus onePerformance

medium System graph quality Integrity conf 1.00 Likely N+1 query: `for rs in …` triggers a query per row — diagnostico_gastos.py:74

diagnostico_gastos.py:74 N plus onePerformance

medium System graph quality Integrity conf 1.00 Likely N+1 query: `for servicio in …` triggers a query per row — diagnose_agenda.py:66

The loop iterates a Django queryset and accesses `servicio.servicio.duracion` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 q…

diagnose_agenda.py:66 N plus onePerformance

medium System graph quality Integrity conf 1.00 Likely N+1 query: `for servicio in …` triggers a query per row — diagnostico_servicios_web.py:38

The loop iterates a Django queryset and accesses `servicio.nombre.lower` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 querie…

diagnostico_servicios_web.py:38 N plus onePerformance

medium System graph quality Integrity conf 1.00 Likely N+1 query: `for servicio in …` triggers a query per row — fix_tipo_servicio.py:42

fix_tipo_servicio.py:42 N plus onePerformance

medium System graph quality Integrity conf 1.00 Likely N+1 query: `for srv in …` triggers a query per row — check_agenda_status.py:41

The loop iterates a Django queryset and accesses `srv.venta_reserva.estado_reserva` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in…

check_agenda_status.py:41 N plus onePerformance

medium System graph quality Integrity conf 1.00 Likely N+1 query: `for srv in …` triggers a query per row — check_agenda_status.py:59

The loop iterates a Django queryset and accesses `srv.servicio.duracion` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 querie…

check_agenda_status.py:59 N plus onePerformance

medium System graph quality Integrity conf 1.00 Likely N+1 query: `for srv in …` triggers a query per row — diagnose_agenda.py:194

The loop iterates a Django queryset and accesses `srv.servicio.nombre` per row, which fires an additional database query each iteration. Add `.select_related('<fk_field>')` for FK / O2O relations or `.prefetch_related('<m2m_or_reverse>')` for many-related lookups, to load everything in 1-2 queries …

diagnose_agenda.py:194 N plus onePerformance

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — verificar_sendgrid.py:32

`requests.get(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.

runtime safetyRobustness

medium System graph security Coverage conf 1.00 No auth library detected

The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.

auth

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 24 placeholder/mock markers across 8 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.

Mock dataIncompleteGenerated repo pattern

low System graph quality Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.

Repo hardeningGenerated repo pattern

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 3984 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 hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.9-slim

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

Dockerfile:2 containersPinned dependencies

low System graph software Dead code candidate conf 1.00 File has no detected symbols: enable_debug_temp.py

Source file with no class/function declarations — possible config, dead code, or scratch file.

low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 2 places

Functions with the same first-5-line body hash: test_phone_simple.py:test_phone_normalization, test_phone_normalization.py:test_phone_normalization This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're…

3 occurrences

repo-level (3 hits)

duplicatesduplication

low System graph quality Integrity conf 1.00 Near-duplicate function bodies in 3 places

Functions with the same first-5-line body hash: aplicar_migracion_0071.py:packages_distributions, marcar_servicios_pagados.py:packages_distributions, manage.py:packages_distributions This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). …

duplicatesduplication

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 Integrity conf 1.00 Old/deprecated-named symbol `hacer_backup` in fix_serviciobloqueo_seguro.py:22

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph software Dead code conf 1.00 Possibly dead Python function: emit

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

capturar_error_comanda.py:34

low System graph software Dead code conf 1.00 Possibly dead Python function: listar_migraciones_pendientes

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

migrar_sin_validacion.py:28

low System graph software Dead code conf 1.00 Possibly dead Python function: normalize_historical_phones

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

merge_historical_to_current.py:191

low System graph quality Integrity conf 1.00 Stub function `clean_minimo` (body is just `pass`/`return`) — fix_save_method_serviciobloqueo.py:40

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

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/b3aa0edb-df02-4386-8912-869e6ba4433a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/b3aa0edb-df02-4386-8912-869e6ba4433a/

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.