# swagger-api/swagger-ui — health index 87/100 (Excellent)

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

## Category summary

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

## Repository facts

| Field | Value |
|---|---|
| Description | Swagger UI is a collection of HTML, JavaScript, and CSS assets that dynamically generate beautiful documentation from a Swagger-compliant API. |
| Homepage | https://swagger.io |
| Primary language | JavaScript |
| License | Apache-2.0 |
| Stars | 28,917 |
| Forks | 9,263 |
| Created | 2011-07-15 |
| Last push | 2026-07-21 |
| Latest release | v5.32.10 |
| Commits (last year) | 173 |
| Bus factor | 3 |
| Topics | swagger, swagger-ui, swagger-api, swagger-js, rest, rest-api, openapi-specification, oas, openapi, openapi3, hacktoberfest, openapi31, open-source, swagger-oss |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| npm | swagger-ui | 5.32.10 | 638,229 |
| packagist | swagger-api/swagger-ui | v5.32.10 | 1,433,686 |
| npm | swagger-ui-dist | 5.32.10 | 45,317,040 |

## Vitality — 96/100 (Excellent)

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

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

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

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

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

| 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 ~14 days |
| 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 — 90/100 (Excellent)

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

### Popularity & adoption — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | met | 60 / 60 | 28,917 stars |
| Forks | met | 25 / 25 | 9,263 forks |
| Watchers | met | 15 / 15 | 620 watchers |

### Community health — 77/100 (Good)

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Monthly downloads | met | 80 / 80 | 47,388,955 downloads/month across npm, packagist |
| Registry dependents | partial | 13.7 / 20 | 114 packages depend on it |

## Sustainability & Governance — 81/100 (Good)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Bus factor | partial | 36 / 54 | 3 contributor(s) cover half of all commits |
| Commit distribution | partial | 16.3 / 22.5 | top contributor authored 27% of commits |
| Contributor breadth | met | 13.5 / 13.5 | 98 contributors |
| OpenSSF Scorecard: Contributors | met | 10 / 10 | project has 50 contributing companies or organizations |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | partial | 36.3 / 46.8 | 78% of issues closed |
| PR acceptance | partial | 28.7 / 38.2 | 3449/4601 decided PRs merged |
| OpenSSF Scorecard: Code-Review | partial | 9 / 15 | Found 7/11 approved changesets -- score normalized to 6 |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | not met | 0 / 20 | — |
| Owner reach | partial | 23.7 / 25 | 1,957 followers of swagger-api |
| Track record | partial | 23.5 / 25 | 37 public repos, account ~12 yr old |

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

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

## Engineering Quality — 94/100 (Excellent)

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

### Engineering practices — 90/100 (Excellent)

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

### Documentation — 100/100 (Excellent)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | met | 25 / 25 | — |
| Documentation / homepage site | met | 15 / 15 | https://swagger.io |
| Repository description | met | 10 / 10 | — |
| Topics | met | 10 / 10 | 14 topics |
| Wiki | met | 10 / 10 | — |

## Security — 70/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 — 70/100 (Good)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Binary-Artifacts | met | 7.5 / 7.5 | no binaries found in the repo |
| Branch-Protection | excluded | 0 / 7.5 | internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md |
| CI-Tests | met | 2.5 / 2.5 | 26 out of 26 merged PRs checked by a CI test -- score normalized to 10 |
| CII-Best-Practices | partial | 0.5 / 2.5 | badge detected: InProgress |
| Code-Review | partial | 4.5 / 7.5 | Found 7/11 approved changesets -- score normalized to 6 |
| Contributors | met | 2.5 / 2.5 | project has 50 contributing companies or organizations |
| 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 0 issue activity found in the last 90 days -- score normalized to 10 |
| Packaging | met | 5 / 5 | packaging workflow detected |
| Pinned-Dependencies | partial | 1 / 5 | dependency not pinned by hash detected -- score normalized to 2 |
| 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 | not met | 0 / 7.5 | detected GitHub workflow tokens with excessive permissions |
| Vulnerabilities | partial | 2.2 / 7.5 | 7 existing vulnerabilities detected |

### Dependency advisories — 69/100 (Moderate)

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 1884 resolved dependencies against OSV. 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 | partial | 11.8 / 35 | 3 affected: immutable 3.8.3 (high 7.5), immutable 5.1.5 (high 7.5), dompurify 3.4.11 (low) |
| 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 | met | 40 / 40 | no advisory has been public longer than 90 days |

### 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 — 68/100 (Moderate)

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 | CLAUDE.md |
| Machine-readable docs (llms.txt) | not met | 0 / 15 | — |
| Legible commit history | met | 40 / 40 | 46 of 46 human commits state their intent (structured subject or explanatory body) |

### Verify loop (build / test / typecheck) — 55/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | not met | 0 / 18 | — |
| Automated tests | met | 22 / 22 | — |
| Lint / format config | met | 11 / 11 | .eslintrc, .eslintrc.js |
| Static type checking | not met | 0 / 11 | — |
| Reproducible environment | met | 10 / 10 | Dockerfile, lockfile |
| Demonstrated agent practice | partial | 2 / 10 | 1 of the last 100 commits agent-authored or agent-credited |
| Automated maintenance | met | 8 / 8 | 54 of the last 100 commits are automated dependency updates |
| OpenSSF Scorecard: Pinned-Dependencies | partial | 2 / 10 | dependency not pinned by hash detected -- score normalized to 2 |

### Code legibility for models — 55/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | not met | 0 / 45 | JavaScript without a type-check config |
| Manageable file sizes | partial | 54.9 / 55 | 1/660 source files over 60KB |

### Machine-readable interfaces — 80/100 (Good)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| API schema (OpenAPI/GraphQL/proto) | met | 40 / 40 | test/e2e-cypress/static/documents/bugs/5043/swagger.yaml, test/e2e-cypress/static/documents/bugs/5452/openapi.yaml, test/e2e-cypress/static/documents/bugs/5452/swagger.yaml, test/e2e-cypress/static/documents/security/sequential-import-chaining/openapi.yaml, test/e2e-cypress/static/documents/security/sequential-import-chaining/swagger.yaml, test/e2e-cypress/support/helpers/oauth2-server/swagger.yaml |
| MCP server | not met | 0 / 20 | — |
| Runnable examples | met | 40 / 40 | examples, samples |

## Collection warnings

- deps.dev does not index npm:swagger-ui@5.32.10; advisories assessed against the repository dependency graph instead

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