repowisenvidia/nccl

Code health of nvidia/nccl

Repowise scores nvidia/nccl at 5.6 out of 10 for code health, which reads as fair, alongside maintainability 7.6 and static performance 9.9 on the same scale. There are 2,387 open findings across the three pillars, and the lowest-scoring file is transport.cc at 1.0. Scores are computed from complexity, duplication, churn and git fix history, not from a linter.

Findings by severity

259 critical, 644 high, 858 medium, 557 low.

Hotspots

106 files are flagged as hotspots. The top 5:

  • contrib/nccl_ep/nccl_ep.cc: 70 commits in the last 90 days from 15 contributors with 15 recent bug fixes
  • src/dev_runtime.cc: 17 commits in the last 90 days from 13 contributors with 6 recent bug fixes
  • contrib/nccl_ep/include/nccl_ep.h: 41 commits in the last 90 days from 11 contributors with 4 recent bug fixes
  • src/include/nccl_device/impl/gin__funcs.h: 14 commits in the last 90 days from 8 contributors with 1 recent bug fix
  • src/graph/topo.cc: 23 commits in the last 90 days from 15 contributors with 3 recent bug fixes

Lowest-scoring files

  • src/transport.cc: 1.0 out of 10
  • src/proxy.cc: 1.0 out of 10 with 6 bug fixes in the last 180 days
  • src/debug.cc: 1.0 out of 10
  • src/graph/topo.cc: 1.0 out of 10 with 3 bug fixes in the last 180 days
  • src/transport/net_ib/connect.cc: 1.0 out of 10

Checked against bug fixes

Of the 20 files Repowise scores lowest, 14 had a bug fix in the last 180 days. Across all 834 scored files, 12.5% had a bug fix in that window.

Dead code and refactoring

Repowise found 1,118 unused exports. 65 refactoring targets across 65 files would raise the score.

More on nccl: summary and FAQ, codebase overview, architecture.

Related guide: Best dead code detection tools by language