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
196 of your 285 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 66.22s for a 187.7 MB repo slow.
  • Repobility's analysis ran in 35.96s after the clone landed.

NixOS/nixpkgs

https://github.com/NixOS/nixpkgs · scanned 2026-06-06 00:06 UTC (4 days, 3 hours ago) · 10 languages

763 raw signals (249 security + 514 graph) 11/13 scanners ran 78th percentile · Python · medium (20-100K LoC) System graph score 83 (lower by 4)

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

Complete repo analysis

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

JSON
Combined
82.1
/100
Security checks
81
108 findings
System graph
83
100.0% cov · 241 findings
Critical
2
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 65.0 0.15 9.75
security_score 100.0 0.25 25.00
testing_score 82.0 0.20 16.40
documentation_score 66.0 0.15 9.90
practices_score 81.0 0.15 12.15
code_quality 59.0 0.10 5.90
Overall 1.00 79.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 2 High 26 Medium 118 Low 107 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 108 System graph 241 Crowd 0 Layer: Quality 220 Software 68 Security 20 Cicd 2 Api 1 Frontend 22 Network 15 Hardware 1

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 5 places
  • low Near-duplicate function bodies in 3 places repo-level
  • low Near-duplicate function bodies in 4 places repo-level
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 `sample_options_simple_legacy` in pkgs/by-name/ni/n…
  • medium Network/subprocess call without timeout or try/except — pkgs/build-support/fetc…
View all legacy markers findings →
Commented-out code 21 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 pkgs/by-name/ni/nixos-render-docs/src/nixos_r…
  • info Commented-code block (5 lines) in pkgs/by-name/ni/nixos-render-docs/src/nixos_r…
  • info Commented-code block (5 lines) in pkgs/by-name/ni/nixos-rebuild-ng/src/nixos_re…
  • info Commented-code block (5 lines) in pkgs/by-name/ni/nixos-rebuild-ng/src/nixos_re…
  • info Commented-code block (6 lines) in pkgs/by-name/ni/nixos-rebuild-ng/src/nixos_re…
  • info Commented-code block (5 lines) in pkgs/by-name/ni/nixos-rebuild-ng/src/nixos_re…
  • info Commented-code block (15 lines) in pkgs/by-name/au/auto-patchelf/source/auto-pa…
  • info Commented-code block (5 lines) in pkgs/by-name/fl/flatten-references-graph/src/…
  • info Commented-code block (8 lines) in pkgs/by-name/fl/flatten-references-graph/src/…
  • info Commented-code block (6 lines) in pkgs/by-name/gc/gclient2nix/gclient2nix.py:162
  • info Commented-code block (6 lines) in pkgs/by-name/ca/calamares-nixos-extensions/sr…
  • info Commented-code block (11 lines) in pkgs/by-name/lu/luarocks-packages-updater/up…
View all commented-out code findings →
Config drift 2 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.
2 matching findings on this repo
  • high [MINED106] Phantom test coverage: test_switch_to_configuration_with_systemd_run… pkgs/by-name/ni/nixos-rebuild-ng/src/tests/test_n…:823
  • low Very large file: pkgs/by-name/sw/switch-to-configuration-ng/src/main.rs (3105 l…
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/df1ef4a5-237f-47f0-ba66-b6f11e592205/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/df1ef4a5-237f-47f0-ba66-b6f11e592205/

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.