azure/azure-sdk-for-java

0

/ 100

Documentation80
Engineering82
Health100
Java2,558MIT1d ago
Grade a repo

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

This repository is for active development of the Azure SDK for Java. For consumers of the SDK we recommend visiting our public developer docs at https://docs.microsoft.com/java/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-java.

Documentation

80

README12pt65

This repository is large enough that GitHub truncated the file tree. The scan is based on a partial file list, so some checks may under-report.

Contributing guide5pt77

Contributing guide is detailed and thorough.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

82

CI/CD14pt72

CI is configured (.github/workflows/check-enforcer.yml).

Tests18pt80

Test files detected (common/perf-test-core/src/main/java/com/azure/perf/test).

Reproducibility6pt80

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

Linting and formatting5pt100

Java/Kotlin linting configured (.editorconfig).

Issue and PR templates6pt100

Issue or PR templates present.

Project health

100

Dependency manifest6pt100

Dependency manifest found (pom.xml).

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)
  • 2,176
    Forks
  • 1000
    Releaseslatest 4mo ago

Community

  • —
    Community health
  • —
    authors own >50% of commits
  • 2,558
    Watchers

Responsiveness

  • 67d 15h
    Median issue response
  • 10h
    Median PR merge time
  • 534
    Open issues
Repository files25 root entries
  • .config
  • .devcontainer
  • .github
    Good: CI is configured (.github/workflows/check-enforcer.yml).
    Good: Issue or PR templates present.
  • .vscode
  • common
    Good: Test files detected (common/perf-test-core/src/main/java/com/azure/perf/test).
  • docs
  • eng
    Good: Lockfile present (eng/common/spelling/package-lock.json). Installs are reproducible.
  • samples
  • sdk
    Good: Environment pinned via sdk/cosmos/azure-cosmos-benchmark/ctl/Dockerfile.
  • .dockerignore
  • .editorconfig
    Good: Java/Kotlin linting configured (.editorconfig).
  • .gitattributes
  • .gitignore
    Good: .gitignore present.
  • .mcp.json
  • AGENTS.md
  • 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.
  • jetty.xml
  • LICENSE.txt
    Good: Licensed under MIT.
  • NOTICE.txt
  • NuGet.Config
  • pom.xml
    Good: Dependency manifest found (pom.xml).
  • 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.
    Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.
    Good: README links to a live demo or deployed app.
    Good: README includes status badges.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • SECURITY.md
    Good: Security policy present.
  • SUPPORT.md