nvidia/infra-controller

0

/ 100

Documentation85
Engineering93
Health100
Rust204Apache-2.01d ago
Grade a repo

Polished and well engineered. Punching above its star count.

NVIDIA Infra Controller - Hardware Lifecycle Management and multitenant networking

Documentation

85

README12pt70

README is present.

Contributing guide5pt77

Contributing guide is detailed and thorough.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under Apache-2.0.

Engineering

93

Reproducibility6pt80

Lockfile present (Cargo.lock). Installs are reproducible.

CI/CD14pt85

CI is configured (.github/workflows/build-boot-artifacts.yml).

Tests18pt100

Test files detected (bluefield/charts/nico-dpu-agent/tests).

Linting and formatting5pt100

Rust linting configured (rest-api/.golangci.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (Cargo.toml).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • —
    Commits (30d / 90d)
  • 129
    Forks
  • 0
    Releases

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 204
    Watchers

Responsiveness

  • 60d 5h
    Median issue response
  • 3h
    Median PR merge time
  • 475
    Open issues
Repository files48 root entries
  • .cargo
  • .github
    Good: CI is configured (.github/workflows/build-boot-artifacts.yml).
    Good: Issue or PR templates present.
  • .skaffold
  • bluefield
    Good: Test files detected (bluefield/charts/nico-dpu-agent/tests).
    Good: Environment pinned via bluefield/containers/carbide-fmds/Dockerfile.
  • book
  • crates
  • deploy
  • dev
  • docs
  • fern
  • helm
  • helm-prereqs
  • include
  • lints
  • pxe
  • rest-api
    Good: Rust linting configured (rest-api/.golangci.yml).
  • scripts
  • .coderabbit.yaml
  • .dockerignore
  • .envrc
  • .gitignore
    Good: .gitignore present.
  • .gitmodules
  • .local_envrc.example
  • .protolint.yaml
  • .taplo.toml
  • AGENTS.md
  • Cargo.lock
    Good: Lockfile present (Cargo.lock). Installs are reproducible.
  • Cargo.toml
    Good: Dependency manifest found (Cargo.toml).
  • clippy.toml
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CONTRIBUTING.md
    Good: Contributing guide is detailed and thorough.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Good: Contributing guide describes the PR/review workflow.
    Good: Contributing guide includes code examples.
  • Cross.toml
  • deny.toml
  • devspace.yaml
  • docker-compose.yml
  • LICENSE
    Good: Licensed under Apache-2.0.
  • Makefile
  • Makefile-build.toml
  • Makefile-package.toml
  • Makefile.toml
  • pytest.ini
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • rust-toolchain.toml
  • rustfmt.toml
  • SECURITY.md
    Good: Security policy present.
  • skaffold.yml
  • STYLE_GUIDE.md
  • THIRD-PARTY-LICENSES