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.
Sign up free Scan another repo
233 of your 445 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 113.83s for a 215.5 MB repo slow.
  • Repobility's analysis ran in 11.69s after the clone landed.

pathwaycom/pathway

https://github.com/pathwaycom/pathway · scanned 2026-06-05 09:09 UTC (5 days, 19 hours ago) · 10 languages

977 raw signals (431 security + 546 graph) 11/13 scanners ran 90th percentile · Python · large (100-500K LoC) System graph score 58 (higher by 30)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 19 hours ago · v2 · 332 actionable findings from 2 signal sources. 369 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Combined
74.7
/100
Security checks
91
120 findings
System graph
58
100.0% cov · 212 findings
Critical
5
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 85.0 0.15 12.75
security_score 100.0 0.25 25.00
testing_score 93.0 0.20 18.60
documentation_score 88.0 0.15 13.20
practices_score 77.0 0.15 11.55
code_quality 70.0 0.10 7.00
Overall 1.00 88.1
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 5 High 22 Medium 58 Low 149 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 120 System graph 212 Crowd 0 Layer: Software 58 Quality 189 Security 16 Cicd 31 Hardware 33 Api 5

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 repo-level
  • low Near-duplicate function bodies in 10 places
  • low Near-duplicate function bodies in 3 places
View all duplicates & near-duplicates findings →
Legacy markers 2 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.
2 matching findings on this repo
  • low Old/deprecated-named symbol `test_psql_output_snapshot_legacy` in integration_t…
  • low Old/deprecated-named symbol `table_to_legacy` in python/pathway/tests/test_api.…
View all legacy markers findings →
Commented-out code 25 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 (8 lines) in integration_tests/conftest.py:39
  • info Commented-code block (7 lines) in integration_tests/kafka/utils.py:43
  • info Commented-code block (7 lines) in integration_tests/db_connectors/conftest.py:22
  • info Commented-code block (6 lines) in integration_tests/db_connectors/test_dynamodb…
  • info Commented-code block (6 lines) in integration_tests/db_connectors/test_mssql_pa…
  • info Commented-code block (6 lines) in integration_tests/db_connectors/test_leann.py…
  • info Commented-code block (6 lines) in integration_tests/db_connectors/utils.py:96
  • info Commented-code block (6 lines) in integration_tests/db_connectors/test_postgres…
  • info Commented-code block (7 lines) in integration_tests/db_connectors/test_mysql.py…
  • info Commented-code block (6 lines) in integration_tests/db_connectors/test_mssql.py…
  • info Commented-code block (8 lines) in integration_tests/db_connectors/test_milvus_t…
  • info Commented-code block (5 lines) in integration_tests/iceberg/test_iceberg.py:467
View all commented-out code findings →
Config drift 1 finding
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.
1 matching finding on this repo
  • low File has no detected symbols: examples/projects/twitter/services/frontend/webpa…
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/49132254-95b6-49b4-a4d1-8a5245f14672/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/49132254-95b6-49b4-a4d1-8a5245f14672/

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.