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.

baldecash-team/baldecash

https://github.com/baldecash-team/baldecash · scanned 2026-06-17 01:38 UTC (1 month, 2 weeks ago)

227 raw signals (0 security + 227 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -10.6 (diff) · 223 actionable findings from 1 signal source. 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 · 223 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 4 Medium 89 Low 40 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 223 Crowd 0 Layer: Api 1 Frontend 111 Data 1 Security 31 Cicd 2 Quality 77

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.

Legacy markers 3 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.

3 matching findings on this repo

medium Agent authority lacks a verifier contract: .claude/docs/legacy/PROMPT_HERO_SECT… .claude/docs/legacy/PROMPT_HERO_SECTION_BALDECASH…
medium Agent authority lacks a verifier contract: .claude/docs/legacy/WEBFLOW_LAPTOP_I… .claude/docs/legacy/WEBFLOW_LAPTOP_IMAGES.md
low Old/deprecated-named symbol `ApiFilterOptionsLegacy` in src/app/prototipos/0.6/…

View all legacy markers 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 jest.setup.js:46
info Commented-code block (9 lines) in src/app/api/feedback/route.ts:36
info Commented-code block (5 lines) in src/app/prototipos/0.6/[landing]/layout.tsx:6…
info Commented-code block (5 lines) in src/app/prototipos/0.6/[landing]/solicitar/Ga…
info Commented-code block (6 lines) in src/app/prototipos/0.6/[landing]/solicitar/co…
info Commented-code block (10 lines) in src/app/prototipos/0.6/[landing]/solicitar/c…
info Commented-code block (5 lines) in src/app/prototipos/0.6/[landing]/solicitar/co…
info Commented-code block (5 lines) in src/app/prototipos/0.6/[landing]/solicitar/co…
info Commented-code block (5 lines) in src/app/prototipos/0.6/[landing]/catalogo/Cat…
info Commented-code block (7 lines) in src/app/prototipos/0.6/[landing]/catalogo/com…
info Commented-code block (6 lines) in src/app/prototipos/0.6/services/wizardApi.ts:…
info Commented-code block (5 lines) in src/app/prototipos/_shared/hooks/usePrototype…

View all commented-out code findings →

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

5 matching findings on this repo

high Agent instruction/config may expose a secret: .claude/agents/ui-ux-designer.md .claude/agents/ui-ux-designer.md:16
high Agent instruction/config may expose a secret: .claude/agents/nextjs-architectur… .claude/agents/nextjs-architecture-expert.md:137
high Agent instruction/config may expose a secret: .claude/docs/0.5/CONVENTIONS.md .claude/docs/0.5/CONVENTIONS.md:2552
info Commented-code block (5 lines) in src/app/prototipos/_shared/hooks/usePrototype…
medium `fetch()` without try/.catch or AbortSignal — src/app/prototipos/_shared/hooks/…

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/3324b39f-197a-4e2b-a06a-58b8719775aa/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/3324b39f-197a-4e2b-a06a-58b8719775aa/

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.