mongodb/mongo

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.

228 of your 477 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 162.36s for a 205.0 MB repo slow.
Repobility's analysis ran in 381.6s after the clone landed.

https://github.com/mongodb/mongo · scanned 2026-06-05 18:45 UTC (4 days, 18 hours ago) · 10 languages

4815 raw signals (443 security + 4372 graph) 11/13 scanners ran 12th percentile · Javascript · huge (>500K LoC) System graph score 70 (lower by 4)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 18 hours ago · v2 · 2222 actionable findings from 2 signal sources. 395 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 · 2096 findings

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`	17.0	0.20	3.40
`documentation_score`	78.0	0.15	11.70
`practices_score`	54.0	0.15	8.10
`code_quality`	55.0	0.10	5.50
Overall		1.00	66.5

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 82 High 47 Medium 164 Low 368 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 126 System graph 2096 Crowd 0 Layer: Quality 1291 Security 140 Cicd 9 Software 84 Frontend 682 Network 7 Hardware 8 Api 1

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

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

View all duplicates & near-duplicates findings →

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

12 matching findings on this repo

info TODO/FIXME marker in shipping code — jstests/core/timeseries/ddl/rename_timeser…
info TODO/FIXME marker in shipping code — jstests/core/timeseries/ddl/timeseries_col…
info TODO/FIXME marker in shipping code — jstests/core/timeseries/ddl/timeseries_dro…
info TODO/FIXME marker in shipping code — jstests/core/timeseries/ddl/timeseries_clu…
low Old/deprecated-named symbol `aggregate_out_legacy` in jstests/auth/lib/commands…
low Old/deprecated-named symbol `downgradeToLegacy` in jstests/noPassthrough/admiss…
low Old/deprecated-named symbol `getLegacy` in jstests/noPassthrough/query/spill_to…
low Old/deprecated-named symbol `_getStatusLegacy` in jstests/libs/feature_flag_uti…
low Old/deprecated-named symbol `downgradeToLegacy` in jstests/multiVersion/generic…
low Old/deprecated-named symbol `actuallyLegacy` in jstests/multiVersion/genericSet…
low Old/deprecated-named symbol `useLegacy` in jstests/sharding/query/javascript_he…
low Old/deprecated-named symbol `timeseries_collmod_legacy` in jstests/core/timeser…

View all legacy markers findings →

Commented-out code 822 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 (6 lines) in modules_poc/mod_scanner.py:53
info Commented-code block (6 lines) in modules_poc/cindex.py:1047
info Commented-code block (10 lines) in bazel/bazelisk.py:108
info Commented-code block (5 lines) in bazel/workspace_status.py:1
info Commented-code block (5 lines) in bazel/wrapper_hook/compiledb.py:859
info Commented-code block (5 lines) in bazel/wrapper_hook/install_modules.py:110
info Commented-code block (8 lines) in bazel/wrapper_hook/lint.py:931
info Commented-code block (5 lines) in bazel/resmoke/derive_suite_selectors.py:46
info Commented-code block (7 lines) in bazel/resmoke/download_historic_runtimes.py:62
info Commented-code block (7 lines) in evergreen/functions/binaries_extract.py:5
info Commented-code block (13 lines) in jstests/concurrency/fsm_libs/worker_thread.j…
info Commented-code block (15 lines) in jstests/concurrency/fsm_libs/fsm.js:23

View all commented-out code findings →

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

medium No CI/CD configuration found
high [MINED112] FastAPI PATCH buildscripts.resmokelib.testing.hooks.generate_and_che… buildscripts/tests/resmokelib/testing/hooks/test_…:436
high [MINED106] Phantom test coverage: test_validate_clang_tidy_setup_rejects_missin… evergreen/validate_compile_commands_test.py:40
info TODO/FIXME marker in shipping code — jstests/with_mongot/mongotmock/configure_m…
info TODO/FIXME marker in shipping code — jstests/noPassthrough/replication/priority…
info TODO/FIXME marker in shipping code — jstests/noPassthrough/query/agg/agg_config…
info TODO/FIXME marker in shipping code — jstests/hooks/run_reconfig_background.js:30
info TODO/FIXME marker in shipping code — jstests/sharding/drop_configdb.js:9
info TODO/FIXME marker in shipping code — jstests/sharding/convert_to_and_from_confi…
info TODO/FIXME marker in shipping code — jstests/sharding/configsvr_metadata_comman…
info TODO/FIXME marker in shipping code — jstests/sharding/all_shard_and_config_host…
info TODO/FIXME marker in shipping code — jstests/sharding/catalog_shard_mongos_ops_…

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/45d72c0d-64be-4ed4-87e7-e4892f4ee018/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/45d72c0d-64be-4ed4-87e7-e4892f4ee018/

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.