Public record
Software health reportschema 0.27.0 · metrics 2.5.0 · 2026-07-30 17:07 UTC

Zetier / jxl-sys

Rust bindings to libjxl

RustApache-2.0★ 0 stars⑂ 0 forkssince Apr 2025View on GitHub ↗
KindLibraryhow this is determined

Zetier/jxl-sys holds a health index of 54 out of 100, placing it in the Moderate band. It scores highest on Vitality (70/100) and lowest on Engineering Quality (36/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

54
overall / 100
Moderate

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.

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

Ownership

ZetierOrganization
18 followers27 public repossince Mar 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iojxl-sys0.1.11+libjxl-0.11.221,675111 day agojpeg-xljpegxljxllibjpegxllibjxlexternal-ffi-bindingsgraphicsmultimedia

Metrics by category

Vitality

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

70Good · 21% of overall

Development activity

55Moderate
How it's scored
36/36Push recency — last push 1 days ago
4.8/36Commit cadence — 7/52 weeks with commits
12.4/18Commit volume — 23 commits in the last year
2/10OpenSSF Scorecard: Maintained — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
Inputs used
commits_last_year23
human_commit_share0.6
days_since_last_push1
active_weeks_last_year7

Release discipline

92Excellent
How it's scored
27/27Ships releases — 10 releases published
36/36Release recency — latest release 1 days ago
19.8/27Release cadence — a release every ~50.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count10
latest_release_tagv0.1.11+libjxl-0.11.2
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases50.6
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?

41Weak · 17% of overall

Popularity & adoption

1Critical
How it's scored
0/60Stars — 0 stars
0/25Forks — 0 forks
0/15Watchers — 1 watchers
Inputs used
forks0
stars0
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

65Good
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges—
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateno

Ecosystem adoption (downloads)

72Good
How it's scored
57.8/80Monthly downloads — 21,675 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesjxl-sys
dependents—
ecosystemscrates
total_downloads121,163
monthly_downloads21,675
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?

63Moderate · 23% of overall

Maintainer resilience (bus factor)

19Critical
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
2.5/22.5Commit distribution — top contributor authored 89% of commits
4.1/13.5Contributor breadth — 3 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.889

Issue & PR responsiveness

91Excellent
How it's scored
0/42Issue resolution — no issues or no data
27.4/30PR acceptance — 32/35 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
13.5/15OpenSSF Scorecard: Code-Review — Found 10/11 approved changesets -- score normalized to 9
Inputs used
merged_prs32
open_issues0
closed_issues0
prs_merged_7d—
prs_decided_7d—
prs_merged_30d—
prs_decided_30d—
issue_closed_ratio—
closed_unmerged_prs3
first_time_authors_30d—
first_time_prs_merged_30d—
first_time_prs_decided_30d—
Excluded from scoring (no data or not applicable): Issue resolution, newcomer_pr_acceptance. Remaining weights renormalized.

Ownership & stewardship

60Moderate
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
9.2/25Owner reach — 18 followers of Zetier
21.3/25Track record — 27 public repos, account ~5 yr old
Inputs used
followers18
owner_typeOrganization
is_verified—
owner_loginZetier
public_repos27
account_age_days1,972

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on crates
35/35Publish recency — latest publish 1 days ago
20/20Version history — 11 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesjxl-sys
ecosystemscrates
any_deprecatedno
min_days_since_publish1

Engineering Quality

Are baseline engineering and documentation practices in place?

36Weak · 19% of overall

Engineering practices

34At Risk
How it's scored
24/24CI workflows — 2 workflow(s)
0/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests — 13 out of 26 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

40Weak
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

53Moderate · 16% of overall

Security posture

53Moderate
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
1.2/2.5CI-Tests — 13 out of 26 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
6.8/7.5Code-Review — Found 10/11 approved changesets -- score normalized to 9
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
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
1.5/7.5Maintained — 3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.3
Excluded from scoring (no data or not applicable): 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.

47Weak · 4% of overall

Agent context & guidance

40Weak
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 24 of 27 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share0.889
agent_instruction_files—
agent_instruction_max_bytes—

Verify loop (build / test / typecheck)

32At Risk
How it's scored
12.6/18One-command bootstrap — Cargo.toml (toolchain convention, no task runner)
0/22Automated tests
0/11Lint / format config
11/11Static type checking — Rust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 45
8/8Automated maintenance — 4 of the last 45 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_testsno
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsCargo.toml
dependency_bot_commit_share0.089

Code legibility for models

100Exceptional
How it's scored
45/45Type-checkable code — Rust (statically typed)
55/55Manageable file sizes — 0/2 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes5,728
source_files_sampled2
oversized_source_files0

Key facts

0GitHub stars
3contributors
23commits, last 12 months
1days since last push
10releases
1bus factor
0open issues
crates.iopackage ecosystems

Data collection warnings

  • deps.dev does not index crates:jxl-sys@0.1.11+libjxl-0.11.2; advisories assessed against the repository dependency graph instead
  • No resolved dependencies carried a version and a supported ecosystem

More detail

OpenSSF Scorecard 5.3 / 10
5.3aggregate

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-07-30 17:07 UTC

10Binary-Artifactsno binaries found in the repo
5Branch-Protectionbranch protection is not maximal on development and all release branches
5CI-Tests13 out of 26 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
9Code-ReviewFound 10/11 approved changesets -- score normalized to 9
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
2Maintained3 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 2
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 5

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

RegistryPackageVersionRelation
crates.ioanyhow—indirect
crates.iobindgen—indirect
crates.iocmake—indirect
crates.ioregex—indirect
crates.iosemver—indirect
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

Related records

Inspected repositories sharing catalogue tags or ecosystems with Zetier/jxl-sys. Read them side by side →

83twistedfall/opencv-rustRust bindings for OpenCVExcellent81LaurenzV/krillaA high-level, ergonomic Rust library for creating PDF documents.Excellent73ComunidadAylas/vorbis-rs🔊 Rust bindings for the best-in-breed C libraries of the Vorbis audio codec and Ogg container encapsulation.Good65milkway/rpic-langA modern reimplementation of the pic graphics language in Rust — SVG/PNG/PDF output, GSAP animation, and an 79-element circuit library. Bindings for Python, R and JS/TS.Good60marc2332/rust-skiaSafe Skia Bindings for RustModerate53tracel-ai/tracel-ashVulkan bindings for RustModerate

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.5.0, schema v0.27.0 — full methodology · metrics wiki.

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