marin-community/marin

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.

230 of your 325 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 28.68s · analysis 21.78s · 80.5 MB · GitHub API rate-limit (preflight)

https://github.com/marin-community/marin · scanned 2026-06-05 20:17 UTC (4 days, 14 hours ago) · 10 languages

1740 raw signals (312 security + 1428 graph) 11/13 scanners ran 94th percentile · Python · large (100-500K LoC) System graph score 52 (higher by 38)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 14 hours ago · v2 · 589 actionable findings from 2 signal sources. 433 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 · 492 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`	100.0	0.20	20.00
`documentation_score`	99.0	0.15	14.85
`practices_score`	78.0	0.15	11.70
`code_quality`	55.0	0.10	5.50
Overall		1.00	89.8

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 0 High 36 Medium 77 Low 261 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 97 System graph 492 Crowd 0 Layer: Software 74 Quality 431 Security 21 Cicd 13 Frontend 3 Network 4 Hardware 14 Api 29

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

2 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

View all duplicates & near-duplicates findings →

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

3 matching findings on this repo

low Old/deprecated-named symbol `loaded_legacy` in tests/test_grug_checkpointing.py…
low Old/deprecated-named symbol `_str_hash_legacy` in rust/dupekit/tests/bench/test…
low Old/deprecated-named symbol `_maybe_migrate_legacy` in lib/iris/src/iris/cluste…

View all legacy markers findings →

Commented-out code 160 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 tests/test_slice_cache.py:19
info Commented-code block (6 lines) in tests/processing/classification/deduplication…
info Commented-code block (9 lines) in tests/processing/classification/deduplication…
info Commented-code block (9 lines) in tests/processing/classification/deduplication…
info Commented-code block (11 lines) in tests/processing/classification/deduplicatio…
info Commented-code block (9 lines) in tests/processing/classification/deduplication…
info Commented-code block (7 lines) in scripts/verify_smoke_v0.py:241
info Commented-code block (5 lines) in scripts/python_libs_package.py:151
info Commented-code block (5 lines) in scripts/logscan.py:6
info Commented-code block (6 lines) in scripts/ops/cross_region.py:491
info Commented-code block (7 lines) in scripts/ops/storage/distributed_scan.py:72
info Commented-code block (5 lines) in scripts/ops/storage/report.py:223

View all commented-out code findings →

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

high [MINED106] Phantom test coverage: test_lm_config_with_train_urls_allowed_out_of… tests/test_training.py:65
low File has no detected symbols: lib/finelog/dashboard/rsbuild.config.ts
low File has no detected symbols: lib/finelog/dashboard/tailwind.config.ts
low File has no detected symbols: lib/iris/dashboard/rsbuild.config.ts
low File has no detected symbols: lib/iris/dashboard/tailwind.config.ts
low File has no detected symbols: lib/iris/src/iris/rpc/config_pb2.py
low File has no detected symbols: infra/status-page/vite.config.ts
low File has no detected symbols: infra/status-page/eslint.config.js
low File has no detected symbols: experiments/test_dpo_generation_config.py
low Very large file: lib/iris/tests/cluster/providers/test_config.py (1838 lines)
low Very large file: lib/iris/src/iris/cluster/config.py (1228 lines)
info Commented-code block (5 lines) in lib/iris/src/iris/cluster/config.py:827

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/3265d277-6008-4ed1-b5b4-1344b358efda/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/3265d277-6008-4ed1-b5b4-1344b358efda/

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.