# Azure/azure-sdk-for-java — health index 97/100 (Exceptional)

> Inspection of the public repository Azure/azure-sdk-for-java by inspect.software. It holds a health index of 97 out of 100, placing it in the Exceptional band. The index is a signal derived from publicly visible practice, not a warranty, a security audit, or an endorsement, and it is independent of payment.

- Repository: https://github.com/Azure/azure-sdk-for-java
- Report page: https://inspect.software/software/Azure/azure-sdk-for-java
- Full JSON report: https://inspect.software/api/repositories/Azure/azure-sdk-for-java/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/a/Azure/azure-sdk-for-java.svg
- Inspected: 2026-08-21
- Methodology: metrics 2.10.0, report schema 0.34.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 21% | 100/100 | Exceptional |
| Community & Adoption | 17% | 94/100 | Exceptional |
| Sustainability & Governance | 23% | 89/100 | Excellent |
| Engineering Quality | 19% | 75/100 | Good |
| Security | 16% | 64/100 | Moderate |
| AI Readiness | 4% | 79/100 | Good |

The weighted overall 85 is calibrated to 97 on the published index scale (record calibration 2026-08-02).

## Repository facts

| Field | Value |
|---|---|
| Description | 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. |
| Classification | network-service, library |
| Primary language | Java |
| License | MIT |
| Stars | 2,567 |
| Forks | 2,184 |
| Created | 2011-12-06 |
| Last push | 2026-08-21 |
| Latest release | com.azure.resourcemanager+azure-resourcemanager-storagesync_1.0.0 |
| Commits (last year) | 1,989 |
| Bus factor | 9 |
| Topics | java, azure-services, azure-resources, media, azure, azure-sdk, hacktoberfest |

## Vitality — 100/100 (Exceptional)

Is the project alive — is code being written and are releases shipping? Weight: 21% of the overall index.

### Development activity — 100/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Push recency | met | 36 / 36 | last push 0 days ago |
| Commit cadence | met | 36 / 36 | 52/52 weeks with commits |
| Commit volume | met | 18 / 18 | 1989 commits in the last year |
| OpenSSF Scorecard: Maintained | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Release discipline — 100/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | met | 27 / 27 | 100 releases published |
| Release recency | met | 36 / 36 | latest release 0 days ago |
| Release cadence | met | 27 / 27 | a release every ~0.3 days |
| OpenSSF Scorecard: Signed-Releases | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Abandonment — 100/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Project is still maintained | met | 100 / 100 | last human commit 1 days ago |

## Community & Adoption — 94/100 (Exceptional)

Does the project have users, downloads, attention, and a welcoming setup for contributors? Weight: 17% of the overall index.

### Popularity & adoption — 95/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 55.3 / 60 | 2,567 stars |
| Forks | met | 25 / 25 | 2,184 forks |
| Watchers | partial | 14.8 / 15 | 464 watchers |

### Community health — 92/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 22.5 / 22.5 | — |
| License | met | 22.5 / 22.5 | recognized license (MIT) |
| CONTRIBUTING guide | met | 18 / 18 | — |
| Code of conduct | met | 13.5 / 13.5 | — |
| Issue template | not met | 0 / 7.2 | — |
| PR template | met | 6.3 / 6.3 | — |

## Sustainability & Governance — 89/100 (Excellent)

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep? Weight: 23% of the overall index.

### Maintainer resilience (bus factor) — 95/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Bus factor | met | 54 / 54 | 9 contributor(s) cover half of all commits |
| Commit distribution | partial | 18 / 22.5 | top contributor authored 20% of commits |
| Contributor breadth | met | 13.5 / 13.5 | 98 contributors |
| OpenSSF Scorecard: Contributors | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Issue & PR responsiveness — 72/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | partial | 40.7 / 42 | 97% of issues closed |
| PR acceptance | partial | 20.4 / 30 | 25733/37892 decided PRs merged |
| Newcomer PR acceptance | not met | 0 / 13 | 0/1 first-time contributors' PRs merged in 30d |
| OpenSSF Scorecard: Code-Review | excluded | 0 / 15 | OpenSSF Scorecard unavailable |

### Ownership & stewardship — 100/100 (Exceptional)

Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | excluded | 0 / 20 | verified-domain status not read for this organization |
| Owner reach | met | 25 / 25 | 15,202 followers of Azure |
| Track record | met | 25 / 25 | 2731 public repos, account ~12 yr old |

## Engineering Quality — 75/100 (Good)

Are baseline engineering and documentation practices in place? Weight: 19% of the overall index.

### Engineering practices — 68/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | met | 24 / 24 | 11 workflow(s) |
| Tests present | met | 24 / 24 | — |
| Linter config | not met | 0 / 16 | — |
| Pre-commit hooks | not met | 0 / 9.6 | — |
| .editorconfig | met | 6.4 / 6.4 | — |
| OpenSSF Scorecard: CI-Tests | excluded | 0 / 20 | OpenSSF Scorecard unavailable |

### Documentation — 85/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | met | 25 / 25 | — |
| Documentation / homepage site | not met | 0 / 15 | — |
| Repository description | met | 10 / 10 | — |
| Topics | met | 10 / 10 | 7 topics |
| Wiki | met | 10 / 10 | — |

## Security — 64/100 (Moderate)

Are visible security and supply-chain practices strong, with no malicious dependency and no unresolved high-risk jurisdiction exposure? Weight: 16% of the overall index.

### Security posture — 55/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Security policy (SECURITY.md) | met | 30 / 30 | — |
| Dependabot config | not met | 0 / 25 | — |
| Dependency lockfiles | met | 25 / 25 | package-lock.json |
| CodeQL workflow | not met | 0 / 20 | — |

### Dependency advisories — 100/100 (Exceptional)

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 1101 resolved dependencies against OSV; 43 could not be assessed (no resolved version, an unsupported ecosystem, or beyond the reported package list). This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Direct dependencies free of known advisories | met | 35 / 35 | no direct dependency carries a known advisory |
| Indirect dependencies free of known advisories | excluded | 0 / 25 | transitive set not separable from development and test dependencies in this scope |
| No advisories left outstanding | excluded | 0 / 40 | no advisory carries a publication date |

### Malicious dependencies — 100/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| No dependency reported as a malicious package | met | 100 / 100 | no dependency is reported as a malicious package |

### High-Risk Jurisdiction Exposure — 100/100 (Exceptional)

Only high-confidence self-published location evidence affects this multiplier. Ambiguous matches are review-only; country evidence is not proof of nationality, citizenship, legal registration, malicious intent, or sanctions status.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Policy exposure multiplier | met | 100 / 100 | no confirmed policy-scope location match |

## AI Readiness — 79/100 (Good)

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight: agent tooling is a real maintenance signal, but its absence must never gate the top of the scale (calibration saturates at raw 91, so 100/100 remains reachable with AI Readiness at zero).

### Agent context & guidance — 85/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Agent instructions | met | 45 / 45 | .github/copilot-instructions.md, AGENTS.md, sdk/cosmos/AGENTS.md |
| Machine-readable docs (llms.txt) | not met | 0 / 15 | — |
| Legible commit history | met | 40 / 40 | 55 of 55 human commits state their intent (structured subject or explanatory body) |

### Verify loop (build / test / typecheck) — 73/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | partial | 12.6 / 18 | common/perf-test-core/pom.xml, eng/automation/changelog/pom.xml, eng/bomgenerator/pom.xml (toolchain convention, no task runner) |
| Automated tests | met | 22 / 22 | — |
| Lint / format config | not met | 0 / 11 | — |
| Static type checking | met | 11 / 11 | Java (statically typed) |
| Reproducible environment | met | 10 / 10 | devcontainer, Dockerfile, lockfile |
| Demonstrated agent practice | met | 10 / 10 | 34 of the last 100 commits agent-authored or agent-credited |
| Automated maintenance | not met | 0 / 8 | no automated dependency updates observed |
| OpenSSF Scorecard: Pinned-Dependencies | excluded | 0 / 10 | OpenSSF Scorecard unavailable |

### Code legibility for models — 99/100 (Exceptional)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | met | 45 / 45 | Java (statically typed) |
| Manageable file sizes | partial | 53.8 / 55 | 504/23846 source files over 60KB |

### Machine-readable interfaces — 60/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| API schema (OpenAPI/GraphQL/proto) | not met | 0 / 40 | — |
| MCP server | met | 20 / 20 | — |
| Runnable examples | met | 40 / 40 | notebooks, sample, samples |

## Collection warnings

- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
- First-time contributor figures cover 12 of 15 authors (cap 12)
- File tree truncated by GitHub API; file-based signals may be incomplete
- Could not fetch maven package 'com.azure.tools:bomGenerator' from its registry
- Could not fetch maven package 'com.azure:perf-test-core' from its registry
- Advisory severity resolved for 120 of 132 advisories (lookup cap); the remainder are reported as unknown severity
- OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

## What this report is

inspect.software measures public repositories against a single published, versioned methodology and reports the result as a 1–100 health index. Findings are signals derived from what is visible in public repository data — they are not a security audit, a warranty, or an endorsement, and no result depends on payment.

- Methodology, formulas and weights: https://inspect.software/methodology.md
- What a result does and does not claim: https://inspect.software/wiki/signals-not-warranties.md
- Rating bands: https://inspect.software/wiki/scoring-bands.md
- Corrections: https://inspect.software/contact.md
- Index of all documents: https://inspect.software/llms.txt