Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-04 18:51 UTC

A11yance / aria-query

Programmatic access to the ARIA specification

JavaScriptApache-2.0★ 303 stars⑂ 45 forkssince Jan 2017View on GitHub ↗

A11yance/aria-query holds a health index of 31 out of 100, placing it in the At Risk band. It scores highest on Community & Adoption (66/100) and lowest on Vitality (20/100). It was last updated 606 days ago. A single contributor accounts for most of its recent work.

31
overall / 100
At Risk

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.

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

Ownership

A11yanceOrganization
15 followers5 public repossince Aug 2015

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
npmaria-query5.3.2500,675,24129682 days agoaccessibilityaria

Metrics by category

Vitality

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

20At Risk · 21% of overall
How it's scored
0/36Push recencylast push 606 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share0.7
days_since_last_push606
active_weeks_last_year0
How it's scored
16.2/27Ships releases32 version tags (no GitHub releases)
7.2/36Release recencylatest release 682 days ago
19.8/27Release cadencea release every ~84.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count32
latest_release_tagv5.3.2
releases_from_tagsyes
days_since_latest_release682
mean_days_between_releases84.1
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?

66Good · 17% of overall
How it's scored
40.2/60Stars303 stars
13.7/25Forks45 forks
5.8/15Watchers12 watchers
Inputs used
forks45
stars303
watchers12
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges1
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com
has_pull_request_templateno
How it's scored
80/80Monthly downloads500,675,241 downloads/month across npm
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesaria-query
dependents
ecosystemsnpm
total_downloads
monthly_downloads500,675,241
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?

60Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
6.6/22.5Commit distributiontop contributor authored 70% of commits
13.5/13.5Contributor breadth17 contributors
10/10OpenSSF Scorecard: Contributorsproject has 54 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled17
top_contributor_share0.705
How it's scored
37/42Issue resolution88% of issues closed
10.9/30PR acceptance198/545 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 9/23 approved changesets -- score normalized to 3
Inputs used
merged_prs198
open_issues6
closed_issues44
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.88
closed_unmerged_prs347
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
8.7/25Owner reach15 followers of A11yance
17.7/25Track record5 public repos, account ~10 yr old
Inputs used
followers15
owner_typeOrganization
is_verified
owner_loginA11yance
public_repos5
account_age_days4,010
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on npm
14/35Publish recencylatest publish 682 days ago
20/20Version history29 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesaria-query
ecosystemsnpm
any_deprecatedno
min_days_since_publish682

Engineering Quality

Are baseline engineering and documentation practices in place?

58Moderate · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter config.eslintrc
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 13 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics3 topics
0/10Wiki
Inputs used
topicsaccessibility, aria, wcag2
has_wikino
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?

57Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0/2.5CI-Tests0 out of 13 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-ReviewFound 9/23 approved changesets -- score normalized to 3
2.5/2.5Contributorsproject has 54 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
4/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
0/5SASTSAST tool is not run on all commits -- score normalized to 0
4.5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 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.

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.

41Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
22.1/40Legible commit history29 of 70 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.414
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance30 of the last 100 commits are automated dependency updates
8/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.3
How it's scored
0/45Type-checkable codeJavaScript without a type-check config
54.7/55Manageable file sizes1/182 source files over 60KB
Inputs used
primary_languageJavaScript
largest_source_bytes87,932
source_files_sampled182
oversized_source_files1

Key facts

303GitHub stars
17contributors
0commits, last 12 months
606days since last push
32releases
1bus factor
6open issues
npmpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

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

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.

010203040504422017-052021-102026-04
Major 5Minor 7Patch 15

Each point covers 9 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-08-04 18:51 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 13 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/23 approved changesets -- score normalized to 3
10Contributorsproject has 54 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
8Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
0SASTSAST tool is not run on all commits -- score normalized to 0
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 22

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

RegistryPackageVersionRelation
npm@babel/cli^7.25.6indirect
npm@babel/core^7.25.2indirect
npm@babel/eslint-parser^7.25.1indirect
npm@babel/node^7.25.0indirect
npm@babel/plugin-transform-react-jsx^7.25.2indirect
npm@babel/preset-env^7.25.4indirect
npm@babel/preset-flow^7.24.7indirect
npm@babel/register^7.24.6indirect
npmarray.from^1.1.6indirect
npmarray.prototype.some^1.1.6indirect
npmbabel-plugin-module-resolver^5.0.2indirect
npmcommander^9.4.1indirect
npmdeep-equal-json^1.0.0indirect
npmeslint^8.57.0indirect
npmeslint-plugin-flowtype^8.0.3indirect
npmflow-bin^0.191.0indirect
npmmock-property^1.1.0indirect
npmnyc^10.3.2indirect
npmobject-inspect^1.13.2indirect
npmobject.values^1.2.0indirect
npmrimraf^2.7.1indirect
npmtape^5.9.0indirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.31.0 — full methodology · metrics wiki.

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