# qos-ch/logback — health index 70/100 (Good)

> Inspection of the public repository qos-ch/logback by inspect.software. It holds a health index of 70 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/qos-ch/logback
- Report page: https://inspect.software/software/qos-ch/logback
- Full JSON report: https://inspect.software/api/repositories/qos-ch/logback/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/q/qos-ch/logback.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% | 93/100 | Excellent |
| Community & Adoption | 18% | 80/100 | Good |
| Sustainability & Governance | 24% | 57/100 | Moderate |
| Engineering Quality | 20% | 51/100 | Moderate |
| Security | 16% | 68/100 | Moderate |
| AI Readiness | not counted | 54/100 | Moderate |

## Repository facts

| Field | Value |
|---|---|
| Description | The reliable, generic, fast and flexible logging framework for Java. |
| Homepage | http://logback.qos.ch |
| Primary language | Java |
| Stars | 3,231 |
| Forks | 1,365 |
| Created | 2009-08-20 |
| Last push | 2026-07-17 |
| Latest release | v_1.5.38 |
| Commits (last year) | 192 |
| Bus factor | 1 |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| maven | ch.qos.logback:logback-core | 1.5.38 | — |
| maven | ch.qos.logback:logback-classic | 1.5.38 | — |
| maven | ch.qos.logback:logback-examples | 1.5.38 | — |

## Vitality — 93/100 (Excellent)

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Push recency | met | 36 / 36 | last push 4 days ago |
| Commit cadence | partial | 23.5 / 36 | 34/52 weeks with commits |
| Commit volume | met | 18 / 18 | 192 commits in the last year |
| OpenSSF Scorecard: Maintained | met | 10 / 10 | 30 commit(s) and 8 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 | 23 releases published |
| Release recency | met | 36 / 36 | latest release 12 days ago |
| Release cadence | met | 27 / 27 | a release every ~16.1 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 4 days ago |

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

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 56.9 / 60 | 3,231 stars |
| Forks | met | 25 / 25 | 1,365 forks |
| Watchers | partial | 11.9 / 15 | 141 watchers |

### Community health — 64/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 22.5 / 22.5 | — |
| License | partial | 16.9 / 22.5 | license file present, not a recognized license |
| CONTRIBUTING guide | met | 18 / 18 | — |
| Code of conduct | not met | 0 / 13.5 | — |
| Issue template | not met | 0 / 7.2 | — |
| PR template | not met | 0 / 6.3 | — |

## Sustainability & Governance — 57/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) — 36/100 (At risk)

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

### Issue & PR responsiveness — 38/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | partial | 20.8 / 46.8 | 44% of issues closed |
| PR acceptance | partial | 17.5 / 38.2 | 238/521 decided PRs merged |
| OpenSSF Scorecard: Code-Review | not met | 0 / 15 | Found 2/30 approved changesets -- score normalized to 0 |

### Ownership & stewardship — 66/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | not met | 0 / 20 | — |
| Owner reach | partial | 14.6 / 25 | 105 followers of qos-ch |
| Track record | partial | 21.1 / 25 | 17 public repos, account ~14 yr old |

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

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

## Engineering Quality — 51/100 (Moderate)

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

### Engineering practices — 48/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | met | 24 / 24 | 1 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 | not met | 0 / 20 | 0 out of 2 merged PRs checked by a CI test -- score normalized to 0 |

### Documentation — 55/100 (Moderate)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| README | met | 30 / 30 | — |
| Documentation directory | not met | 0 / 25 | — |
| Documentation / homepage site | met | 15 / 15 | http://logback.qos.ch |
| Repository description | met | 10 / 10 | — |
| Topics | not met | 0 / 10 | — |
| Wiki | not met | 0 / 10 | — |

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

Excluded from scoring (no data or not applicable): Branch-Protection, 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 | 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 | not met | 0 / 2.5 | 0 out of 2 merged PRs checked by a CI test -- score normalized to 0 |
| 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 2/30 approved changesets -- score normalized to 0 |
| 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 | not met | 0 / 7.5 | no update tool detected |
| Fuzzing | met | 5 / 5 | project is fuzzed |
| License | partial | 2.2 / 2.5 | license file detected |
| Maintained | met | 7.5 / 7.5 | 30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10 |
| Packaging | excluded | 0 / 5 | packaging workflow not detected |
| Pinned-Dependencies | not met | 0 / 5 | dependency not pinned by hash detected -- score normalized to 0 |
| SAST | not met | 0 / 5 | SAST tool is not run on all commits -- score normalized to 0 |
| 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 | met | 7.5 / 7.5 | 0 existing vulnerabilities detected |

### Dependency advisories — 82/100 (Good)

Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 41 resolved dependencies against OSV; 32 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 | partial | 21.6 / 35 | 1 affected: ch.qos.logback:logback-core 1.5.25 (moderate 4.8) |
| 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 — 54/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 — 49/100 (At risk)

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

### Verify loop (build / test / typecheck) — 46/100 (At risk)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | partial | 12.6 / 18 | logback-access/pom.xml, logback-classic-blackbox/pom.xml, logback-classic-misc/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 | not met | 0 / 10 | — |
| Demonstrated agent practice | not met | 0 / 10 | no agent-authored commits among the last 100 |
| Automated maintenance | not met | 0 / 8 | no automated dependency updates observed |
| OpenSSF Scorecard: Pinned-Dependencies | not met | 0 / 10 | dependency not pinned by hash detected -- score normalized to 0 |

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

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

### Machine-readable interfaces — 40/100 (At risk)

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

## Collection warnings

- Could not fetch maven package 'ch.qos.logback:logback-classic-misc' from its registry
- Could not fetch maven package 'ch.qos.logback:logback-core-blackbox' from its registry
- Could not fetch maven package 'ch.qos.logback:logback-classic-blackbox' 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