Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-09 18:03 UTC

ash-project / ash_graphql

The extension for building GraphQL APIs with Ash

ElixirCustom license★ 97 stars⑂ 101 forkssince May 2020View on GitHub ↗

ash-project/ash_graphql holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Vitality (93/100) and lowest on AI Readiness (52/100). It was last updated 7 days ago. A single contributor accounts for most of its recent work.

86
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.

86
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 72 is calibrated to 86 on the published index scale (record calibration 2026-08-02).

Ownership

Ash FrameworkOrganization
388 followers61 public repossince Dec 2019

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Hexash_graphql1.11.017,90620310 days ago

Metrics by category

Vitality

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

93Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 7 days ago
24.9/36Commit cadence — 36/52 weeks with commits
18/18Commit volume — 127 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year127
human_commit_share0.89
days_since_last_push7
active_weeks_last_year36

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 14 releases published
36/36Release recency — latest release 10 days ago
27/27Release cadence — a release every ~43.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count14
latest_release_tagv1.11.0
releases_from_tagsno
days_since_latest_release10
mean_days_between_releases43.2
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

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

69Good · 17% of overall
How it's scored
32.2/60Stars — 97 stars
16.7/25Forks — 101 forks
4.7/15Watchers — 8 watchers
Inputs used
forks101
stars97
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

86Excellent
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes
How it's scored
56.7/80Monthly downloads — 17,906 downloads/month across hex
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesash_graphql
dependents—
ecosystemshex
total_downloads445,117
monthly_downloads17,906
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

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

70Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
4.7/22.5Commit distribution — top contributor authored 79% of commits
13.5/13.5Contributor breadth — 72 contributors
10/10OpenSSF Scorecard: Contributors — project has 18 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled72
top_contributor_share0.792
How it's scored
36.5/42Issue resolution — 87% of issues closed
27.5/30PR acceptance — 320/349 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
4.5/15OpenSSF Scorecard: Code-Review — Found 9/28 approved changesets -- score normalized to 3
Inputs used
merged_prs320
open_issues15
closed_issues99
prs_merged_7d0
prs_decided_7d0
prs_merged_30d5
prs_decided_30d5
issue_closed_ratio0.868
closed_unmerged_prs29
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
18.6/25Owner reach — 388 followers of ash-project
25/25Track record — 61 public repos, account ~6 yr old
Inputs used
followers388
owner_typeOrganization
is_verifiedno
owner_loginash-project
public_repos61
account_age_days2,471

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on hex
35/35Publish recency — latest publish 10 days ago
20/20Version history — 203 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesash_graphql
ecosystemshex
any_deprecatedno
min_days_since_publish10

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://hexdocs.pm/ash_graphql
10/10Repository description
10/10Topics — 3 topics
10/10Wiki
Inputs used
topicsash, graphql, elixir
has_wikiyes
homepagehttps://hexdocs.pm/ash_graphql
docs_sitehttps://hexdocs.pm/ash_graphql
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

60Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0/2.5CI-Tests — 0 out of 11 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-Review — Found 9/28 approved changesets -- score normalized to 3
2.5/2.5Contributors — project has 18 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 — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
3.5/5SAST — SAST tool is not run on all commits -- score normalized to 7
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 20 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.7
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
14.8/35Direct dependencies free of known advisories — 2 affected: ash 3.32.1 (moderate 6.8), igniter 0.8.3 (unknown)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
40/40No advisories left outstanding — no advisory has been public longer than 90 days
Inputs used
sourceosv
advisories20
affected_packages3
assessed_packages63
unassessed_packages0
affected_by_severityhigh 1, moderate 1, unknown 1
direct_affected_packages2
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 63 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.

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.

52Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 81 of 89 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.91
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — mix.exs (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
8/10Demonstrated agent practice — 4 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 11 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesmix.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0.04
toolchain_manifestsmix.exs
dependency_bot_commit_share0.11
How it's scored
0/45Type-checkable code — Elixir without a type-check config
54.5/55Manageable file sizes — 2/242 source files over 60KB
Inputs used
primary_languageElixir
largest_source_bytes187,552
source_files_sampled242
oversized_source_files2
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — priv/relay_ids.graphql, priv/root_level_errors.graphql, priv/schema.graphql
0/20MCP server — not applicable to this kind of software
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalno
api_schema_filespriv/relay_ids.graphql, priv/root_level_errors.graphql, priv/schema.graphql
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

97GitHub stars
72contributors
127commits, last 12 months
7days since last push
14releases
1bus factor
15open issues
Hexpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 101 ⇿
0Stars
101Forks
12Releases

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.

02040608010012010132020-082023-082026-08
Major 0Minor 3Patch 9

Each point covers 6 days.

OpenSSF Scorecard 5.7 / 10
5.7aggregate

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-09 18:02 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal 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
0CI-Tests0 out of 11 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 9/28 approved changesets -- score normalized to 3
10Contributorsproject has 18 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
7SASTSAST tool is not run on all commits -- score normalized to 7
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities20 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
Hexash~> 3.5 and >= 3.5.13mix.exs
Hexabsinthe_plug~> 1.4mix.exs
Hexabsinthe~> 1.7mix.exs
Hexabsinthe_phoenix~> 2.0mix.exs
Hexjason~> 1.2mix.exs
Hexigniter~> 0.5 and >= 0.5.28mix.exs
Hexspark>= 2.2.10mix.exs
All dependencies 63

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

RegistryPackageVersionRelation
Hexabsinthe1.11.0direct
Hexabsinthe_phoenix2.0.5direct
Hexabsinthe_plug1.5.10direct
Hexash3.32.1direct
Hexigniter0.8.3direct
Hexjason1.4.5direct
Hexspark2.7.2direct
Hexbenchee1.5.1indirect
Hexbunt1.0.0indirect
Hexcredo1.7.19indirect
Hexcrux0.1.4indirect
Hexdecimal3.1.1indirect
Hexdeep_merge1.0.2indirect
Hexdialyxir1.4.7indirect
Hexearmark_parser1.4.45indirect
Hexecto3.14.2indirect
Hexerlex0.2.8indirect
Hexets0.9.0indirect
Hexex_ast0.13.1indirect
Hexex_check0.16.0indirect
Hexex_doc0.40.3indirect
Hexfile_system1.1.1indirect
Hexfinch0.23.0indirect
Hexgit_cli0.3.0indirect
Hexgit_ops2.12.2indirect
Hexglob_ex0.1.12indirect
Hexhpax1.0.4indirect
Hexiterex0.1.2indirect
Hexmakeup1.2.2indirect
Hexmakeup_elixir1.0.1indirect
Hexmakeup_erlang1.1.0indirect
Hexmime2.0.7indirect
Hexmint1.9.3indirect
Hexmix_audit2.1.5indirect
Hexmix_test_watch1.4.0indirect
Hexmultigraph0.16.1-mg.4indirect
Hexnimble_options1.1.1indirect
Hexnimble_parsec1.4.2indirect
Hexnimble_pool1.1.0indirect
Hexowl0.13.1indirect
Hexphoenix1.8.9indirect
Hexphoenix_pubsub2.2.0indirect
Hexphoenix_template1.0.4indirect
Hexphx_new1.8.13indirect
Hexplug1.20.3indirect
Hexplug_crypto2.2.0indirect
Hexreactor1.0.6indirect
Hexreq0.7.4indirect
Hexrewrite1.3.0indirect
Hexsimple_sat0.1.4indirect
Hexsobelow0.15.0indirect
Hexsourceror1.12.2indirect
Hexspitfire0.4.0indirect
Hexsplode0.3.2indirect
Hexstatistex1.1.1indirect
Hexstream_data1.4.0indirect
Hextelemetry1.4.2indirect
Hextext_diff0.1.0indirect
Hexwebsock0.5.3indirect
Hexwebsock_adapter0.6.0indirect
Hexyamerl0.10.0indirect
Hexyaml_elixir2.12.2indirect
Hexymlr5.1.6indirect
Dependency advisories 3

This repository publishes no package the index resolves, so its own dependency graph was assessed — 63 packages, which also include development and test pins that never ship: 3 carry known advisories, of which 2 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
mint1.9.3indirecthigh21.10.0
ash3.32.1directmoderate173.33.0
igniter0.8.3directunknown10.8.4

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

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 — Hex.