Good shape overall. A few tweaks would push it into the top tier.

Azure HPC/AI VM Images

Documentation

70

Contributing guide5pt30

Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).

Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.

Install and run instructions9pt45

README documents how to install the project.

README12pt90

README is present.

License6pt100

Licensed under MIT.

Engineering

67

Linting and formatting5pt0

No linter or formatter config found.

Add a linter config such as .eslintrc.json, .prettierrc, ruff.toml, or .golangci.yml to enforce consistent code style.

Issue and PR templates6pt0

No issue or PR templates found (−100 pts).

Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.

Reproducibility6pt70

Lockfile present (components/torset-tool/requirements.txt). Installs are reproducible.

Tests18pt80

Test files detected (tests).

CI/CD14pt100

CI is configured (azure-pipelines.yml).

Project health

100

Dependency manifest6pt100

Dependency manifest found (components/torset-tool/requirements.txt).

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)
  • 109
    Forks
  • 86
    Releaseslatest 5y ago

Community

  • Community health
  • authors own >50% of commits
  • 128
    Watchers

Responsiveness

  • 12d 6h
    Median issue response
  • <1h
    Median PR merge time
  • 25
    Open issues
Repository files16 root entries
  • azure-pipelines
  • components
    Good: Lockfile present (components/torset-tool/requirements.txt). Installs are reproducible.
    Good: Dependency manifest found (components/torset-tool/requirements.txt).
  • distros
  • packer
  • partners
  • tests
    Good: Test files detected (tests).
  • topology
  • utils
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • azure-pipelines.yml
    Good: CI is configured (azure-pipelines.yml).
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • LICENSE
    Good: Licensed under MIT.
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    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.
    Issue: No run or usage instructions found (−45 pts).Fix: Add a section showing how to start or use the project.
  • SECURITY.md
    Good: Security policy present.
  • versions.json