azure/azure-sdk-for-go
Grade a repo

87

/ 100

GradeB

A well-known project done right. Strong docs and solid engineering throughout.

Top 18% of 5,156 graded repos

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:

Documentation90
Engineering79
Health100
Go1,828MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

11 to address
  1. 1
    Tests18pt

    Wire your tests to a documented command (e.g. a test script in your build config) so the suite is reproducible.

  2. 2
    CI/CD14pt

    Add a step like `run: npm test`, `run: pytest`, or `run: tox` to your workflow file.

  3. 3
    CI/CD14pt

    Add a lint step to catch style issues automatically.

  4. 4
    CI/CD14pt

    Add `tsc --noEmit`, `mypy`, or `cargo check` to catch type errors before they merge.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

90

Contributing guide5pt80

Contributing guide is detailed and thorough.

README12pt90

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

79

CI/CD14pt57

CI is configured (.github/workflows/copilot-setup-steps.yml).

Tests18pt80

Test files detected (eng/tools/generator/changelog/changelog_filter_test.go).

Reproducibility6pt92

Lockfile present (eng/common/spelling/package-lock.json). Installs are reproducible.

Linting and formatting5pt100

Linter or formatter configured (eng/.golangci.yml).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (eng/common/spelling/package.json).

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)
  • 991
    Forks
  • 1000
    Releaseslatest 2y ago

Community

  • 87% - Good
    Community health
  • -
    authors own >50% of commits
  • 1,828
    Watchers

Responsiveness

  • 7h
    Median issue response
  • 7h
    Median PR merge time
  • 310
    Open issues
Repository files19 root entries
  • .config
  • .devcontainer
  • .github
    Good: CI is configured (.github/workflows/copilot-setup-steps.yml).
    Good: Dependabot configured for devcontainers.
    Good: Issue or PR templates present.
  • .vscode
  • documentation
  • eng
    Good: 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
  • sdk
    Good: Environment pinned via sdk/containers/azcontainerregistry/testdata/Dockerfile.
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • AGENTS.md
  • CODE_OF_CONDUCT.md
    Good: Code of conduct present.
  • CodeQL.yml
  • 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.
    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.txt
    Good: Licensed under MIT.
  • NOTICE.txt
  • 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.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • SUPPORT.md
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/azure/azure-sdk-for-go)](https://www.repo-grade.com/report/azure/azure-sdk-for-go)

More graded Go repos