Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-11 10:31 UTC

micronaut-projects / micronaut-graphql

A repository for Micronaut and GraphQL integrations

Java · GroovyApache-2.0★ 88 stars⑂ 47 forkssince Dec 2018View on GitHub ↗

micronaut-projects/micronaut-graphql holds a health index of 88 out of 100, placing it in the Excellent band. It scores highest on AI Readiness (83/100) and lowest on Community & Adoption (64/100). It was last updated today. 2 contributors account for most of its recent work.

88
overall / 100
Excellent

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

88
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

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

Ownership

Micronaut FrameworkOrganization · verified domain
801 followers149 public repossince Feb 2018

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

82Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
11.1/36Commit cadence — 16/52 weeks with commits
18/18Commit volume — 120 commits in the last year
10/10OpenSSF Scorecard: Maintained — 20 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year120
human_commit_share0.55
days_since_last_push0
active_weeks_last_year16

Release discipline

93Exceptional
How it's scored
27/27Ships releases — 47 releases published
36/36Release recency — latest release 58 days ago
19.8/27Release cadence — a release every ~86 days
10/10OpenSSF Scorecard: Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts.
Inputs used
releases_count47
latest_release_tagv5.1.0
releases_from_tagsno
days_since_latest_release58
mean_days_between_releases86

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

64Moderate · 17% of overall
How it's scored
31.5/60Stars — 88 stars
13.9/25Forks — 47 forks
6.5/15Watchers — 16 watchers
Inputs used
forks47
stars88
watchers16
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
7.2/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateyes
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

78Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
14.8/22.5Commit distribution — top contributor authored 34% of commits
13.5/13.5Contributor breadth — 26 contributors
10/10OpenSSF Scorecard: Contributors — project has 15 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled26
top_contributor_share0.342
How it's scored
34.6/42Issue resolution — 82% of issues closed
22.3/30PR acceptance — 503/677 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
7.5/15OpenSSF Scorecard: Code-Review — Found 9/18 approved changesets -- score normalized to 5
Inputs used
merged_prs503
open_issues13
closed_issues61
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.824
closed_unmerged_prs174
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
20.9/25Owner reach — 801 followers of micronaut-projects
25/25Track record — 149 public repos, account ~8 yr old
Inputs used
followers801
owner_typeOrganization
is_verifiedyes
owner_loginmicronaut-projects
public_repos149
account_age_days3,118

Engineering Quality

Are baseline engineering and documentation practices in place?

67Good · 19% of overall
How it's scored
24/24CI workflows — 7 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests — 20 out of 21 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 1 topics
10/10Wiki
Inputs used
topicscommunity-driven
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

76Good · 16% of overall
How it's scored
6.8/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — no data
2.2/2.5CI-Tests — 20 out of 21 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-Review — Found 9/18 approved changesets -- score normalized to 5
2.5/2.5Contributors — project has 15 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 20 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
5/5Pinned-Dependencies — all dependencies are pinned
1.5/5SAST — SAST tool is not run on all commits -- score normalized to 3
5/5Security-Policy — security policy file detected
7.5/7.5Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate7.6
Excluded from scoring (no data or not applicable): Branch-Protection. Remaining weights renormalized.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

83Excellent · 4% of overall
How it's scored
45/45Agent instructions — .github/instructions/coding.instructions.md, .github/instructions/docs.instructions.md
0/15Machine-readable docs (llms.txt)
33/40Legible commit history — 34 of 55 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.618
agent_instruction_files.github/instructions/coding.instructions.md, .github/instructions/docs.instructions.md
agent_instruction_max_bytes8,161
How it's scored
12.6/18One-command bootstrap — build.gradle, buildSrc/build.gradle, docs-examples/hello-world-groovy/build.gradle (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Java (statically typed)
0/10Reproducible environment
10/10Demonstrated agent practice — 8 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 45 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.08
toolchain_manifestsbuild.gradle, buildSrc/build.gradle, docs-examples/hello-world-groovy/build.gradle, docs-examples/hello-world-java/build.gradle, docs-examples/hello-world-kotlin/build.gradle, examples/chat/build.gradle, examples/jwt-security/build.gradle, examples/todo-java-tools/build.gradle, examples/todo-spqr/build.gradle, graphql-bom/build.gradle, graphql/build.gradle, test-suite-graal/build.gradle, test-suite-jackson/build.gradle.kts, test-suite-serde/build.gradle.kts
dependency_bot_commit_share0.45
How it's scored
45/45Type-checkable code — Java (statically typed)
55/55Manageable file sizes — 0/78 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes18,747
source_files_sampled78
oversized_source_files0
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — docs-examples/hello-world-groovy/src/main/resources/schema.graphqls, docs-examples/hello-world-java/src/main/resources/schema.graphqls, docs-examples/hello-world-kotlin/src/main/resources/schema.graphqls, examples/chat/src/main/resources/schema.graphqls, examples/jwt-security/src/main/resources/schema.graphqls, examples/todo-java-tools/src/main/resources/schema.graphqls, graphql/src/test/resources/schema.graphqls, graphql/src/test/resources/websocket.graphql, test-suite-graal/src/main/resources/schema.graphqls
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — example, examples
Inputs used
example_dirsexample, examples
has_mcp_signalno
api_schema_filesdocs-examples/hello-world-groovy/src/main/resources/schema.graphqls, docs-examples/hello-world-java/src/main/resources/schema.graphqls, docs-examples/hello-world-kotlin/src/main/resources/schema.graphqls, examples/chat/src/main/resources/schema.graphqls, examples/jwt-security/src/main/resources/schema.graphqls, examples/todo-java-tools/src/main/resources/schema.graphqls, graphql/src/test/resources/schema.graphqls, graphql/src/test/resources/websocket.graphql, test-suite-graal/src/main/resources/schema.graphqls
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

88GitHub stars
26contributors
120commits, last 12 months
0days since last push
47releases
2bus factor
13open issues
Mavenpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 47 ⇿
0Stars
47Forks
45Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

010203040504622019-032022-102026-05
Major 5Minor 17Patch 10

Each point covers 7 days.

OpenSSF Scorecard 7.6 / 10
7.6aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-09-11 10:30 UTC

9Binary-Artifactsbinaries present in source code
n/aBranch-Protectioninternal error: error during GetBranch(5.0.x): error during branchesHandler.query: 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
9CI-Tests20 out of 21 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 9/18 approved changesets -- score normalized to 5
10Contributorsproject has 15 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained20 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
3SASTSAST tool is not run on all commits -- score normalized to 3
10Security-Policysecurity policy file detected
10Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 0

Full resolved dependency set from the GitHub dependency graph: 0 direct and 0 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies to assess

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics.