# microsoft/beachball — health index 72/100 (Good)

> Inspection of the public repository microsoft/beachball by inspect.software. It holds a health index of 72 out of 100, placing it in the Good 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/microsoft/beachball
- Report page: https://inspect.software/software/microsoft/beachball
- Full JSON report: https://inspect.software/api/repositories/microsoft/beachball/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/m/microsoft/beachball.svg
- Inspected: 2026-07-23
- Methodology: metrics 1.13.0, report schema 0.27.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 22% | 54/100 | Moderate |
| Community & Adoption | 18% | 81/100 | Good |
| Sustainability & Governance | 24% | 68/100 | Moderate |
| Engineering Quality | 20% | 86/100 | Excellent |
| Security | 16% | 78/100 | Good |
| AI Readiness | not counted | 85/100 | Excellent |

## Repository facts

| Field | Value |
|---|---|
| Description | The Sunniest Semantic Version Bumper |
| Homepage | https://microsoft.github.io/beachball |
| Primary language | TypeScript |
| License | MIT |
| Stars | 812 |
| Forks | 92 |
| Created | 2019-06-25 |
| Last push | 2026-07-23 |
| Commits (last year) | 252 |
| Bus factor | 1 |
| Topics | mp, yarn, semver, git, registry |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| npm | p-graph | 2.0.0 | 120,075 |
| npm | beachball | 2.65.5 | 150,445 |
| npm | proper-changelog | 0.1.1 | 179 |

## Vitality — 54/100 (Moderate)

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

### Development activity — 89/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Push recency | met | 36 / 36 | last push 0 days ago |
| Commit cadence | partial | 24.9 / 36 | 36/52 weeks with commits |
| Commit volume | met | 18 / 18 | 252 commits in the last year |
| OpenSSF Scorecard: Maintained | met | 10 / 10 | 30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10 |

### Release discipline — 1/100 (Critical)

Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | not met | 0 / 27 | no releases published |
| Release recency | not met | 0 / 36 | no releases |
| Release cadence | not met | 0 / 27 | no releases |
| OpenSSF Scorecard: Signed-Releases | excluded | 0 / 10 | no releases found |

### Abandonment — 100/100 (Excellent)

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

## Community & Adoption — 81/100 (Good)

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

### Popularity & adoption — 68/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 47.2 / 60 | 812 stars |
| Forks | partial | 16.3 / 25 | 92 forks |
| Watchers | partial | 4.7 / 15 | 8 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 | — |

### Ecosystem adoption (downloads) — 86/100 (Excellent)

Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Monthly downloads | partial | 69 / 80 | 150,624 downloads/month across npm |
| Registry dependents | excluded | 0 / 20 | not reported by this ecosystem |

## Sustainability & Governance — 68/100 (Moderate)

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

### Maintainer resilience (bus factor) — 43/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Bus factor | partial | 9 / 54 | 1 contributor(s) cover half of all commits |
| Commit distribution | partial | 10.8 / 22.5 | top contributor authored 52% of commits |
| Contributor breadth | met | 13.5 / 13.5 | 51 contributors |
| OpenSSF Scorecard: Contributors | met | 10 / 10 | project has 3 contributing companies or organizations -- score normalized to 10 |

### Issue & PR responsiveness — 59/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | partial | 31.8 / 46.8 | 68% of issues closed |
| PR acceptance | partial | 27 / 38.2 | 750/1063 decided PRs merged |
| OpenSSF Scorecard: Code-Review | not met | 0 / 15 | Found 0/22 approved changesets -- score normalized to 0 |

### Ownership & stewardship — 80/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | not met | 0 / 20 | — |
| Owner reach | met | 25 / 25 | 125,668 followers of microsoft |
| Track record | met | 25 / 25 | 8218 public repos, account ~12 yr old |

### Package maintenance — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Published & resolvable | met | 25 / 25 | 2 package(s) on npm |
| Publish recency | met | 35 / 35 | latest publish 28 days ago |
| Version history | met | 20 / 20 | 277 published versions |
| Not deprecated | met | 20 / 20 | active, not deprecated or yanked |

## Engineering Quality — 86/100 (Excellent)

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | met | 24 / 24 | 3 workflow(s) |
| Tests present | met | 24 / 24 | — |
| Linter config | met | 16 / 16 | eslint.config.js, eslint.config.mjs |
| Pre-commit hooks | not met | 0 / 9.6 | — |
| .editorconfig | not met | 0 / 6.4 | — |
| OpenSSF Scorecard: CI-Tests | met | 20 / 20 | 29 out of 29 merged PRs checked by a CI test -- score normalized to 10 |

### Documentation — 90/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | met | 25 / 25 | — |
| Documentation / homepage site | met | 15 / 15 | https://microsoft.github.io/beachball |
| Repository description | met | 10 / 10 | — |
| Topics | met | 10 / 10 | 5 topics |
| Wiki | not met | 0 / 10 | — |

## Security — 78/100 (Good)

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 — 73/100 (Good)

Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Binary-Artifacts | met | 7.5 / 7.5 | no binaries found in the repo |
| Branch-Protection | partial | 3 / 7.5 | branch protection is not maximal on development and all release branches |
| CI-Tests | met | 2.5 / 2.5 | 29 out of 29 merged PRs checked by a CI test -- score normalized to 10 |
| CII-Best-Practices | not met | 0 / 2.5 | no effort to earn an OpenSSF best practices badge detected |
| Code-Review | not met | 0 / 7.5 | Found 0/22 approved changesets -- score normalized to 0 |
| Contributors | met | 2.5 / 2.5 | project has 3 contributing companies or organizations -- score normalized to 10 |
| Dangerous-Workflow | met | 10 / 10 | no dangerous workflow patterns detected |
| Dependency-Update-Tool | met | 7.5 / 7.5 | update tool detected |
| Fuzzing | not met | 0 / 5 | project is not fuzzed |
| License | met | 2.5 / 2.5 | license file detected |
| Maintained | met | 7.5 / 7.5 | 30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10 |
| Packaging | excluded | 0 / 5 | packaging workflow not detected |
| Pinned-Dependencies | partial | 4 / 5 | dependency not pinned by hash detected -- score normalized to 8 |
| SAST | met | 5 / 5 | SAST tool is run on all commits |
| Security-Policy | met | 5 / 5 | security policy file detected |
| Signed-Releases | excluded | 0 / 7.5 | no releases found |
| Token-Permissions | met | 7.5 / 7.5 | GitHub workflow tokens follow principle of least privilege |
| Vulnerabilities | partial | 3 / 7.5 | 6 existing vulnerabilities detected |

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

Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the npm:beachball@2.65.5 runtime dependency closure — what installing the published package pulls in — 74 packages. 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 | met | 25 / 25 | no indirect dependency carries a known advisory |
| No advisories left outstanding | excluded | 0 / 40 | no advisory carries a publication date |

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

| 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 (Excellent)

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 — 85/100 (Excellent)

How well is the repo equipped to be developed and maintained with AI coding agents? An independent, experimental badge — weight 0.0, so it is surfaced on its own and does not affect the overall health score.

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

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | not met | 0 / 18 | — |
| Automated tests | met | 22 / 22 | — |
| Lint / format config | met | 11 / 11 | eslint.config.js, eslint.config.mjs |
| Static type checking | met | 11 / 11 | .yarn/patches-source/@npmcli-config/user/jsconfig.json, actions/should-release/tsconfig.json, docs/tsconfig.json, packages/beachball/tsconfig.json, packages/esrp-npm-release/tsconfig.json, packages/p-graph/tsconfig.json, packages/proper-changelog/tsconfig.json, renovate/tsconfig.json, scripts/tsconfig.json, yarn-plugins/engines/tsconfig.json, yarn-plugins/npmrc/tsconfig.json |
| Reproducible environment | met | 10 / 10 | lockfile |
| Demonstrated agent practice | met | 10 / 10 | 14 of the last 100 commits agent-authored or agent-credited |
| Automated maintenance | met | 8 / 8 | 24 of the last 100 commits are automated dependency updates |
| OpenSSF Scorecard: Pinned-Dependencies | partial | 8 / 10 | dependency not pinned by hash detected -- score normalized to 8 |

### Code legibility for models — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | met | 45 / 45 | TypeScript (statically typed) |
| Manageable file sizes | partial | 54.7 / 55 | 2/377 source files over 60KB |

## Collection warnings

- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
- Could not fetch npm package '@microsoft/beachball-change-file-skill' from its registry
- Could not fetch npm package '@microsoft/m365-renovate-config' from its registry
- npm package 'p-graph' points at a different repository (https://github.com/microsoft/p-graph); excluded from ecosystem scoring
- Could not fetch npm package '@microsoft/beachball-yarn-plugin-npmrc' from its registry
- Could not fetch npm package '@microsoft/beachball-yarn-plugin-engines' from its registry
- Could not fetch npm package '@microsoft/beachball-action-should-release' from its registry
- Could not fetch npm package '@microsoft/beachball-action-install-beachball' from its registry
- Could not fetch npm package '@microsoft/beachball-action-check-for-modified-files' from its registry

## 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