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.

vencil/Dynamic-Alerting-Integrations

https://github.com/vencil/Dynamic-Alerting-Integrations · scanned 2026-06-16 00:48 UTC (2 months, 1 week ago)

433 raw signals (0 security + 433 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 278 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 3 Medium 81 Low 56 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 278 Crowd 0 Layer: Software 11 Frontend 6 Network 59 Hardware 13 Security 8 Cicd 5 Quality 176

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 3 places repo-level
low Near-duplicate function bodies in 4 places
low Near-duplicate function bodies in 5 places

View all duplicates & near-duplicates findings →

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

6 matching findings on this repo

low Old/deprecated-named symbol `patch_legacy` in tests/ops/test_patch_config.py:9
low Old/deprecated-named symbol `exec_time_ms_legacy` in tests/shared/test_helm_cha…
low Old/deprecated-named symbol `another_legacy` in tests/lint/test_check_metric_di…
low Old/deprecated-named symbol `test_root_readme_pair_legacy` in tests/lint/test_c…
low Old/deprecated-named symbol `has_legacy` in scripts/tools/ops/_grar_validate.py…
low Old/deprecated-named symbol `patch_legacy` in scripts/tools/ops/patch_config.py…

View all legacy markers findings →

Commented-out code 131 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 (7 lines) in tests/conftest.py:41
info Commented-code block (6 lines) in tests/ops/test_lint_custom_rules.py:379
info Commented-code block (5 lines) in tests/ops/test_benchmark.py:21
info Commented-code block (5 lines) in tests/ops/test_git_check_lock.py:51
info Commented-code block (6 lines) in tests/ops/test_property_based.py:492
info Commented-code block (7 lines) in tests/shared/_go_mutation_pilot.py:161
info Commented-code block (6 lines) in tests/shared/_mutation_pilot.py:417
info Commented-code block (8 lines) in tests/shared/test_tool_exit_codes.py:62
info Commented-code block (5 lines) in tests/shared/test_property_tools.py:160
info Commented-code block (5 lines) in tests/dx/test_scaffold_jsx_dep.py:82
info Commented-code block (6 lines) in tests/dx/test_analyze_bench_history.py:466
info Commented-code block (6 lines) in tests/dx/test_generate_tenant_fixture.py:200

View all commented-out code findings →

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

9 matching findings on this repo

low Possibly dead Python function: add_config_dir_arg scripts/tools/_lib_io.py:178
low Possibly dead Python function: render_configmap scripts/tools/dx/generate_rulepack_configmaps.py:…
high Insecure pattern 'eval_used' in components/threshold-exporter/app/pkg/config/cu… components/threshold-exporter/app/pkg/config/cust…:76
low Old/deprecated-named symbol `patch_legacy` in tests/ops/test_patch_config.py:9
info Commented-code block (8 lines) in tests/e2e/config-lint.spec.ts:45
info Commented-code block (5 lines) in tests/e2e/eslint.config.mjs:3
low Old/deprecated-named symbol `patch_legacy` in scripts/tools/ops/patch_config.py…
info Commented-code block (5 lines) in scripts/tools/ops/config_diff.py:38
info Commented-code block (5 lines) in tools/portal/src/interactive/tools/config-lin…

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/b8ba2bce-8793-4c01-84b7-01d56075f66a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/b8ba2bce-8793-4c01-84b7-01d56075f66a/

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.