Good shape overall. A few tweaks would push it into the top tier.
Azure HPC/AI VM Images
Documentation
70
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.
README documents how to install the project.
README is present.
Licensed under MIT.
Engineering
67
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.
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.
Lockfile present (components/torset-tool/requirements.txt). Installs are reproducible.
Test files detected (tests).
CI is configured (azure-pipelines.yml).
Project health
100
Dependency manifest found (components/torset-tool/requirements.txt).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 109Forks
- 86Releaseslatest 5y ago
Community
- —Community health
- —authors own >50% of commits
- 128Watchers
Responsiveness
- 12d 6hMedian issue response
- <1hMedian PR merge time
- 25Open issues
Repository files16 root entries
- azure-pipelines
- componentsGood: Lockfile present (components/torset-tool/requirements.txt). Installs are reproducible.Good: Dependency manifest found (components/torset-tool/requirements.txt).
- distros
- packer
- partners
- testsGood: Test files detected (tests).
- topology
- utils
- .gitattributes
- .gitignoreGood: .gitignore present.
- azure-pipelines.ymlGood: CI is configured (azure-pipelines.yml).
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- LICENSEGood: Licensed under MIT.
- README.mdGood: 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.mdGood: Security policy present.
- versions.json