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.

rosenvladimirov/l10n-bulgaria

https://github.com/rosenvladimirov/l10n-bulgaria · scanned 2026-06-15 23:55 UTC (2 months, 3 weeks ago)

160 raw signals (0 security + 160 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 5 Medium 16 Low 72 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 148 Crowd 0 Layer: Software 22 Frontend 17 Security 10 Quality 77 Api 22

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.

Duplicates & near-duplicates 4 findings

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

4 matching findings on this repo

low Near-duplicate function bodies in 2 places repo-level
low Near-duplicate function bodies in 4 places
low Near-duplicate function bodies in 5 places
low Near-duplicate function bodies in 3 places

View all duplicates & near-duplicates findings →

Legacy markers 1 finding

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.

1 matching finding on this repo

low Old/deprecated-named symbol `_l10n_bg_save_z_record_from_legacy` in l10n_bg_erp…

View all legacy markers findings →

Commented-out code 53 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 l10n_bg_report_theme/models/res_company.py:123
info Commented-code block (6 lines) in l10n_bg_reports_audit/models/account_account_…
info Commented-code block (6 lines) in l10n_bg_hr_holidays/models/hr_leave_allocatio…
info Commented-code block (6 lines) in l10n_bg_hr_holidays/models/hr_leave_balance_y…
info Commented-code block (10 lines) in l10n_bg_hr_holidays/migrations/19.0.1.10.3/p…
info Commented-code block (6 lines) in l10n_bg_hr_holidays/migrations/19.0.1.10.2/po…
info Commented-code block (6 lines) in l10n_bg_hr_holidays/migrations/19.0.1.10.1/po…
info Commented-code block (8 lines) in l10n_bg_hr_holidays/migrations/19.0.1.10.4/po…
info Commented-code block (6 lines) in l10n_bg_2026_classifications/__manifest__.py:…
info Commented-code block (5 lines) in payment_mypos/models/payment_transaction.py:1…
info Commented-code block (5 lines) in payment_mypos/controllers/main.py:43
info Commented-code block (10 lines) in l10n_bg_payroll_classifications/models/bg_mo…

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 Stray `console.log` in TS/JS — l10n_bg_config/static/src/views/form_view.js:58
medium Insecure pattern 'direct_innerhtml_assignment' in l10n_bg_config/static/src/ser… l10n_bg_config/static/src/services/blacklist_serv…:36
info Commented-code block (8 lines) in l10n_bg_erp_net_fp_fleet/models/erpnet_fp_pro…
info Commented-code block (8 lines) in l10n_bg_config/models/chart_template.py:222
info Commented-code block (7 lines) in l10n_bg_config/models/res_company.py:14
low Stub function `_process_config_file` (body is just `pass`/`return`) — l10n_bg_c…
info Commented-code block (6 lines) in l10n_bg_config/models/l10n_bg_vertical.py:345
info Commented-code block (5 lines) in l10n_bg_config/wizards/l10n_bg_vertical_wizar…
info Commented-code block (11 lines) in l10n_bg_config/migrations/19.0.8.5.0/pre-mig…
info Commented-code block (10 lines) in l10n_bg_erp_net_fp/models/pos_config_extensi…

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/e5c00a64-1ba9-4e7d-89e6-e195ccdfe84b/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e5c00a64-1ba9-4e7d-89e6-e195ccdfe84b/

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.