# jaegertracing/jaeger-ui — health index 96/100 (Exceptional)

> Inspection of the public repository jaegertracing/jaeger-ui by inspect.software. It holds a health index of 96 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/jaegertracing/jaeger-ui
- Report page: https://inspect.software/software/jaegertracing/jaeger-ui
- Full JSON report: https://inspect.software/api/repositories/jaegertracing/jaeger-ui/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/j/jaegertracing/jaeger-ui.svg
- Inspected: 2026-07-28
- Methodology: metrics 2.10.0, report schema 0.27.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 21% | 96/100 | Exceptional |
| Community & Adoption | 17% | 84/100 | Excellent |
| Sustainability & Governance | 23% | 82/100 | Excellent |
| Engineering Quality | 19% | 77/100 | Good |
| Security | 16% | 75/100 | Good |
| AI Readiness | 4% | 88/100 | Excellent |

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

## Repository facts

| Field | Value |
|---|---|
| Description | Web UI for Jaeger |
| Classification | web-ui |
| Homepage | http://jaegertracing.io/ |
| Primary language | TypeScript |
| License | Apache-2.0 |
| Stars | 1,513 |
| Forks | 787 |
| Created | 2017-02-23 |
| Last push | 2026-07-28 |
| Latest release | v2.20.0 |
| Commits (last year) | 678 |
| Bus factor | 3 |
| Topics | opentracing, distributed-tracing, jaeger, sre, trace, apm, tracing, monitoring, site-reliability-engineering, javascript, react, reactjs, typescript, ui, hacktoberfest |

## Vitality — 96/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 | 678 commits in the last year |
| OpenSSF Scorecard: Maintained | met | 10 / 10 | 30 commit(s) and 11 issue activity found in the last 90 days -- score normalized to 10 |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | met | 27 / 27 | 76 releases published |
| Release recency | met | 36 / 36 | latest release 8 days ago |
| Release cadence | met | 27 / 27 | a release every ~27 days |
| OpenSSF Scorecard: Signed-Releases | not met | 0 / 10 | Project has not signed or included provenance with any releases. |

### Abandonment — 100/100 (Exceptional)

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

## Community & Adoption — 84/100 (Excellent)

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 51.6 / 60 | 1,513 stars |
| Forks | partial | 24.1 / 25 | 787 forks |
| Watchers | met | 15 / 15 | 1,004 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 | — |

## Sustainability & Governance — 82/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) — 78/100 (Good)

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

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

Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | partial | 35.7 / 42 | 85% of issues closed |
| PR acceptance | partial | 19 / 30 | 2094/3311 decided PRs merged |
| Newcomer PR acceptance | excluded | 0 / 13 | no first-time contributor's PR decided in 30d |
| OpenSSF Scorecard: Code-Review | partial | 13.5 / 15 | Found 29/30 approved changesets -- score normalized to 9 |

### Ownership & stewardship — 92/100 (Excellent)

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 | partial | 19.9 / 25 | 580 followers of jaegertracing |
| Track record | partial | 23.4 / 25 | 36 public repos, account ~9 yr old |

## Engineering Quality — 77/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 | not met | 0 / 6.4 | — |
| OpenSSF Scorecard: CI-Tests | met | 20 / 20 | 30 out of 30 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 | http://jaegertracing.io/ |
| Repository description | met | 10 / 10 | — |
| Topics | met | 10 / 10 | 15 topics |
| Wiki | not met | 0 / 10 | — |

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Binary-Artifacts | met | 7.5 / 7.5 | no binaries found in the repo |
| Branch-Protection | partial | 6 / 7.5 | branch protection is not maximal on development and all release branches |
| CI-Tests | met | 2.5 / 2.5 | 30 out of 30 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 | partial | 6.8 / 7.5 | Found 29/30 approved changesets -- score normalized to 9 |
| Contributors | met | 2.5 / 2.5 | project has 32 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 11 issue activity found in the last 90 days -- score normalized to 10 |
| Packaging | excluded | 0 / 5 | packaging workflow not detected |
| Pinned-Dependencies | partial | 3.5 / 5 | dependency not pinned by hash detected -- score normalized to 7 |
| SAST | partial | 4.5 / 5 | SAST tool detected but not run on all commits |
| Security-Policy | partial | 4.5 / 5 | security policy file detected |
| Signed-Releases | not met | 0 / 7.5 | Project has not signed or included provenance with any releases. |
| Token-Permissions | not met | 0 / 7.5 | detected GitHub workflow tokens with excessive permissions |
| Vulnerabilities | partial | 3.8 / 7.5 | 5 existing vulnerabilities detected |

### 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 870 resolved dependencies against OSV; 7 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 — 88/100 (Excellent)

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

### Verify loop (build / test / typecheck) — 86/100 (Excellent)

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

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

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

## Collection warnings

- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

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