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.

yaremenko-maksym/CheekyCheeseIT_CRM

https://github.com/yaremenko-maksym/CheekyCheeseIT_CRM · scanned 2026-06-16 01:05 UTC (2 months, 1 week ago)

436 raw signals (0 security + 436 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 416 actionable findings from 1 signal source. 20 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 · 416 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 132 Medium 36 Low 76 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 416 Crowd 0 Layer: Frontend 33 Network 1 Hardware 1 Security 139 Cicd 4 Quality 186 Api 52

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.

Commented-out code 138 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 apps/api/scripts/generate-doc-fixtures.mjs:73
info Commented-code block (7 lines) in apps/api/src/main.ts:19
info Commented-code block (6 lines) in apps/api/src/app.module.ts:67
info Commented-code block (6 lines) in apps/api/src/users/users.archive.spec.ts:13
info Commented-code block (13 lines) in apps/api/src/users/users.service.ts:41
info Commented-code block (5 lines) in apps/api/src/users/users.controller.ts:63
info Commented-code block (5 lines) in apps/api/src/users/users.service.spec.ts:157
info Commented-code block (5 lines) in apps/api/src/users/users-access.service.spec.…
info Commented-code block (5 lines) in apps/api/src/users/users-access.service.ts:76
info Commented-code block (6 lines) in apps/api/src/notifications/notifications.cont…
info Commented-code block (5 lines) in apps/api/src/notifications/notifications.serv…
info Commented-code block (5 lines) in apps/api/src/config/env.ts:14

View all commented-out code findings →

Config drift 133 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

high Agent instruction/config may expose a secret: .claude/briefs/pm-brief-invoice-s… .claude/briefs/pm-brief-invoice-signing.md:238
high Agent instruction/config may expose a secret: .claude/briefs/2026-05-21-users-a… .claude/briefs/2026-05-21-users-archive-refactor-…:668
high Agent instruction/config may expose a secret: .claude/briefs/2026-05-20-profile… .claude/briefs/2026-05-20-profile-pages-plan.md:1185
high Agent instruction/config may expose a secret: .claude/state/pm-state.json .claude/state/pm-state.json:13
high Agent instruction/config may expose a secret: .claude/rules/ecc/typescript/secu… .claude/rules/ecc/typescript/security.md:17
high Agent instruction/config may expose a secret: .claude/tasks/task-fix-junior-ut-… .claude/tasks/task-fix-junior-ut-round5.progress.…:1
high Agent instruction/config may expose a secret: .claude/tasks/task-hr-rbac-teamma… .claude/tasks/task-hr-rbac-teammate-access.progre…:1
high Agent instruction/config may expose a secret: .claude/tasks/task-drop-phase3-fr… .claude/tasks/task-drop-phase3-frontend.progress.…:1
high Agent instruction/config may expose a secret: .claude/tasks/archive/task-payout… .claude/tasks/archive/task-payout-auto-on-validat…:1
high Agent instruction/config may expose a secret: .claude/tasks/archive/task-drop-p… .claude/tasks/archive/task-drop-phase4c-pending-s…:1
high Agent instruction/config may expose a secret: .claude/tasks/archive/task-junior… .claude/tasks/archive/task-junior-ux-3-cleanup.md:1
high Agent instruction/config may expose a secret: .claude/tasks/archive/task-drop-p… .claude/tasks/archive/task-drop-phase2-backend.pr…:1

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/22181881-70e1-4f81-b3d0-2c5fc1ab23d5/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/22181881-70e1-4f81-b3d0-2c5fc1ab23d5/

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.