# javaee/servlet-spec — health index 12/100 (Critical)

> Inspection of the public repository javaee/servlet-spec by inspect.software. It holds a health index of 12 out of 100, placing it in the Critical 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/javaee/servlet-spec
- Report page: https://inspect.software/software/javaee/servlet-spec
- Full JSON report: https://inspect.software/api/repositories/javaee/servlet-spec/report
- Badge: https://raw.githubusercontent.com/inspect-software/badges/main/v1/j/javaee/servlet-spec.svg
- Inspected: 2026-07-28
- Methodology: metrics 2.1.0, report schema 0.27.0 (https://inspect.software/methodology.md)

## Category summary

| Category | Weight | Index | Band |
|---|---|---|---|
| Vitality | 21% | 10/100 | Critical |
| Community & Adoption | 17% | 62/100 | Moderate |
| Sustainability & Governance | 23% | 47/100 | Weak |
| Engineering Quality | 19% | 27/100 | At Risk |
| Security | 16% | 42/100 | Weak |
| AI Readiness | 4% | 33/100 | At Risk |

The weighted overall 37 is calibrated to 31 on the published index scale (record calibration 2026-08-02). Abandonment Policy applies a 40% multiplier to weighted overall health and gives it a ceiling of 19.

## Repository facts

| Field | Value |
|---|---|
| Description | The API and Issue Tracker for the JCP Standard Java Servlet Specification |
| Homepage | https://javaee.github.io/servlet-spec/ |
| Primary language | Java |
| Stars | 258 |
| Forks | 88 |
| Created | 2017-04-26 |
| Last push | 2018-06-06 |
| Latest release | 4.0.1 |
| Commits (last year) | 0 |
| Bus factor | 1 |
| Archived | yes — the repository is no longer maintained on GitHub |

## Published packages

| Registry | Package | Latest | Monthly downloads |
|---|---|---|---|
| maven | javax.servlet:javax.servlet-api | 4.0.1 | — |

## Vitality — 10/100 (Critical)

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

### Development activity — 1/100 (Critical)

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

### Release discipline — 24/100 (At Risk)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ships releases | partial | 16.2 / 27 | 6 version tags (no GitHub releases) |
| Release recency | not met | 0 / 36 | latest release 3021 days ago |
| Release cadence | partial | 5.4 / 27 | a release every ~494.7 days |
| OpenSSF Scorecard: Signed-Releases | excluded | 0 / 10 | no releases found |

### Abandonment — 40/100 (Weak)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Project is still maintained | partial | 40 / 100 | the repository is archived on GitHub |

## Community & Adoption — 62/100 (Moderate)

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

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Stars | partial | 39.1 / 60 | 258 stars |
| Forks | partial | 16.2 / 25 | 88 forks |
| Watchers | partial | 4.3 / 15 | 7 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 — 47/100 (Weak)

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) — 34/100 (At Risk)

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

### Issue & PR responsiveness — 19/100 (Critical)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Issue resolution | excluded | 0 / 42 | no issues or no data |
| PR acceptance | partial | 8.6 / 30 | 2/7 decided PRs merged |
| Newcomer PR acceptance | excluded | 0 / 13 | no first-time contributor's PR decided in 30d |
| OpenSSF Scorecard: Code-Review | not met | 0 / 15 | Found 2/30 approved changesets -- score normalized to 0 |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Ownership backing | met | 30 / 30 | organization-owned |
| Verified domain | not met | 0 / 20 | — |
| Owner reach | partial | 18.8 / 25 | 408 followers of javaee |
| Track record | met | 25 / 25 | 139 public repos, account ~9 yr old |

### Package maintenance — 69/100 (Good)

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

## Engineering Quality — 27/100 (At Risk)

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

### Engineering practices — 1/100 (Critical)

| Criterion | Status | Points | Detail |
|---|---|---|---|
| CI workflows | not met | 0 / 24 | — |
| Tests present | not met | 0 / 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 — 65/100 (Good)

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

## Security — 42/100 (Weak)

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 — 28/100 (At Risk)

Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Binary-Artifacts | met | 7.5 / 7.5 | no binaries found in the repo |
| Branch-Protection | not met | 0 / 7.5 | branch protection not enabled on development/release branches |
| 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 5 contributing companies or organizations |
| Dangerous-Workflow | excluded | 0 / 10 | no workflows found |
| Dependency-Update-Tool | not met | 0 / 7.5 | no update tool detected |
| Fuzzing | not met | 0 / 5 | project is not fuzzed |
| License | partial | 2.2 / 2.5 | license file detected |
| Maintained | not met | 0 / 7.5 | project is archived |
| Packaging | excluded | 0 / 5 | packaging workflow not detected |
| Pinned-Dependencies | excluded | 0 / 5 | no dependencies found |
| SAST | not met | 0 / 5 | SAST tool is not run on all commits -- score normalized to 0 |
| Security-Policy | not met | 0 / 5 | security policy file not detected |
| Signed-Releases | excluded | 0 / 7.5 | no releases found |
| Token-Permissions | excluded | 0 / 7.5 | No tokens found |
| Vulnerabilities | met | 7.5 / 7.5 | 0 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 9 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 | 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 — 33/100 (At Risk)

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 — 10/100 (Critical)

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

### Verify loop (build / test / typecheck) — 26/100 (At Risk)

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| One-command bootstrap | partial | 12.6 / 18 | pom.xml (toolchain convention, no task runner) |
| Automated tests | not met | 0 / 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 | excluded | 0 / 10 | no dependencies found |

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

| Criterion | Status | Points | Detail |
|---|---|---|---|
| Type-checkable code | met | 45 / 45 | Java (statically typed) |
| Manageable file sizes | partial | 54.3 / 55 | 1/77 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