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.

SmilnitskiyStas/CRMProductSystems

https://github.com/SmilnitskiyStas/CRMProductSystems · scanned 2026-06-16 00:16 UTC (2 months, 2 weeks ago)

75 raw signals (0 security + 75 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 69 actionable findings from 1 signal source. 6 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 · 69 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 8 Medium 27 Low 31 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 69 Crowd 0 Layer: Frontend 17 Hardware 7 Security 11 Cicd 2 Quality 28 Api 4

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 1 finding

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/`.

1 matching finding on this repo

info Commented-code block (6 lines) in worker/src/jobs/fiscalization-retry.job.ts:5

View all commented-out code findings →

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

10 matching findings on this repo

low Icon-only button without accessible name — frontend/features/integrations/compo…
low Icon-only button without accessible name — frontend/features/integrations/compo…
medium CI is configured but no tests are detected
high Agent instruction/config may expose a secret: CLAUDE.md CLAUDE.md:193
high Agent instruction/config may expose a secret: .claude/agents/project-manager.md .claude/agents/project-manager.md:31
high Agent instruction/config may expose a secret: .claude/memory/naming-conventions… .claude/memory/naming-conventions.md:28
high Agent instruction/config may expose a secret: .claude/skills/mobile/setup-navig… .claude/skills/mobile/setup-navigation.md:11
high Agent instruction/config may expose a secret: .claude/skills/workflow/create-ha… .claude/skills/workflow/create-handoff.md:13
high Agent instruction/config may expose a secret: .claude/skills/workflow/create-ta… .claude/skills/workflow/create-task-log.md:13
high Agent instruction/config may expose a secret: .claude/skills/workflow/review-co… .claude/skills/workflow/review-completed-task.md:34

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/da5cd22e-4434-409c-b20b-3ab10560e70c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/da5cd22e-4434-409c-b20b-3ab10560e70c/

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.