A well-known project done right. Strong docs and solid engineering throughout.
This repository is for active development of the Azure SDK for Go. For consumers of the SDK we recommend visiting our public developer docs at:
Documentation
90
Contributing guide is detailed and thorough.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
79
CI is configured (.github/workflows/copilot-setup-steps.yml).
Test files detected (eng/tools/generator/changelog/changelog_filter_test.go).
Lockfile present (eng/common/spelling/package-lock.json). Installs are reproducible.
Linter or formatter configured (eng/.golangci.yml).
Issue or PR templates present.
Project health
100
Dependency manifest found (eng/common/spelling/package.json).
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)
- 991Forks
- 1000Releaseslatest 2y ago
Community
- —Community health
- —authors own >50% of commits
- 1,829Watchers
Responsiveness
- 7hMedian issue response
- 7hMedian PR merge time
- 261Open issues
Repository files19 root entries
- .config
- .devcontainer
- .githubGood: CI is configured (.github/workflows/copilot-setup-steps.yml).Good: Dependabot configured for devcontainers.Good: Issue or PR templates present.
- .vscode
- documentation
- engGood: Test files detected (eng/tools/generator/changelog/changelog_filter_test.go).Good: Linter or formatter configured (eng/.golangci.yml).Good: Lockfile present (eng/common/spelling/package-lock.json). Installs are reproducible.Good: Dependency manifest found (eng/common/spelling/package.json).
- profile
- sdkGood: Environment pinned via sdk/containers/azcontainerregistry/testdata/Dockerfile.
- .gitattributes
- .gitignoreGood: .gitignore present.
- AGENTS.md
- CODE_OF_CONDUCT.mdGood: Code of conduct present.
- CodeQL.yml
- CONTRIBUTING.mdGood: 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.Good: Contributing guide explains how to run tests.Good: Contributing guide describes the PR/review workflow.Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
- LICENSE.txtGood: Licensed under MIT.
- NOTICE.txt
- 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.Good: README documents how to run the project.
- SECURITY.mdGood: Security policy present.
- SUPPORT.md