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

mozilla / authenticator-rs

Rust library to interact with Security Keys, used by Firefox

RustMPL-2.0★ 316 stars⑂ 82 forkssince Mar 2017View on GitHub ↗

mozilla/authenticator-rs holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (84/100) and lowest on AI Readiness (54/100). It was last updated 3 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

MozillaOrganization
10,804 followers2,570 public repossince Sep 2009

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.ioauthenticator0.5.0107,11840330 days agoctap2fidou2fwebauthncryptographyoshardware-support

Metrics by category

Vitality

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

69Good · 21% of overall
How it's scored
36/36Push recency — last push 3 days ago
6.9/36Commit cadence — 10/52 weeks with commits
12.4/18Commit volume — 23 commits in the last year
10/10OpenSSF Scorecard: Maintained — 8 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year23
human_commit_share1
days_since_last_push3
active_weeks_last_year10
How it's scored
27/27Ships releases — 1 releases published
27/36Release recency — latest release 101 days ago
12.6/27Release cadence — cadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count1
latest_release_tagv0.6.0
releases_from_tagsno
days_since_latest_release101
mean_days_between_releases—
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?

63Moderate · 17% of overall
How it's scored
40.5/60Stars — 316 stars
15.9/25Forks — 82 forks
6/15Watchers — 13 watchers
Inputs used
forks82
stars316
watchers13
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MPL-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_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
67.1/80Monthly downloads — 107,118 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesauthenticator
dependents—
ecosystemscrates
total_downloads2,309,335
monthly_downloads107,118
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?

75Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
13.9/22.5Commit distribution — top contributor authored 38% of commits
13.5/13.5Contributor breadth — 31 contributors
10/10OpenSSF Scorecard: Contributors — project has 18 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled31
top_contributor_share0.384
How it's scored
30.6/42Issue resolution — 73% of issues closed
26.9/30PR acceptance — 199/222 decided PRs merged
0/13Newcomer PR acceptance — 0/4 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs199
open_issues38
closed_issues102
prs_merged_7d1
prs_decided_7d1
prs_merged_30d1
prs_decided_30d5
issue_closed_ratio0.729
closed_unmerged_prs23
first_time_authors_30d2
first_time_prs_merged_30d0
first_time_prs_decided_30d4
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
25/25Owner reach — 10,804 followers of mozilla
25/25Track record — 2,570 public repos, account ~16 yr old
Inputs used
followers10,804
owner_typeOrganization
is_verifiedno
owner_loginmozilla
public_repos2,570
account_age_days6,200
How it's scored
25/25Published & resolvable — 1 package(s) on crates
26/35Publish recency — latest publish 330 days ago
20/20Version history — 40 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesauthenticator
ecosystemscrates
any_deprecatedno
min_days_since_publish330

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — .clippy.toml, .flake8, Cargo.toml ([lints]), rustfmt.toml
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests — 15 out of 17 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://crates.io/crates/authenticator
10/10Repository description
10/10Topics — 3 topics
10/10Wiki
Inputs used
topicsu2f, hid, rust
has_wikiyes
homepagehttps://crates.io/crates/authenticator
docs_sitehttps://crates.io/crates/authenticator
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

61Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2/2.5CI-Tests — 15 out of 17 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 18 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
5/5Fuzzing — project is fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 8 commit(s) and 12 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
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_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.1
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.

54Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
3.7/40Legible commit history — 7 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.07
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — Cargo.toml, fuzz/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
11/11Lint / format config — .clippy.toml, .flake8, Cargo.toml ([lints]), rustfmt.toml
11/11Static type checking — Rust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifestsCargo.toml, fuzz/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Rust (statically typed)
52.3/55Manageable file sizes — 5/102 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes132,798
source_files_sampled102
oversized_source_files5
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

316GitHub stars
31contributors
23commits, last 12 months
3days since last push
1releases
2bus factor
38open issues
crates.iopackage 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 ★ / 82 ⇿
0Stars
82Forks
1Releases

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.

0204060801008232017-052021-122026-08
Major 0Minor 1Patch 0

Each point covers 9 days.

OpenSSF Scorecard 6.1 / 10
6.1aggregate

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-18 06:41 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
8CI-Tests15 out of 17 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 18 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained8 commit(s) and 12 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
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
Direct dependencies 22
RegistryPackageVersion constraintManifest
crates.iorand0.8Cargo.toml
crates.iolog0.4Cargo.toml
crates.iolibc0.2Cargo.toml
crates.iorunloop0.1.0Cargo.toml
crates.iobitflags1.0Cargo.toml
crates.ioserde1.0Cargo.toml
crates.ioserde_bytes0.11Cargo.toml
crates.ioserde_cbor0.13Cargo.toml
crates.ioserde_json1.0Cargo.toml
crates.iobytes0.5Cargo.toml
crates.iobase64^0.21Cargo.toml
crates.iosha2^0.10.0Cargo.toml
crates.iocfg-if1.0Cargo.toml
crates.ioopenssl-sys0.9Cargo.toml
crates.ioopenssl0.10Cargo.toml
crates.ionss-rs>=0.12Cargo.toml
crates.iopkcs11-bindings0.1.4Cargo.toml
crates.ioaes0.8Cargo.toml
crates.iocbc0.1Cargo.toml
crates.iorand_core0.6Cargo.toml
crates.iohmac0.12Cargo.toml
crates.iop2560.13Cargo.toml
All dependencies 34

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

RegistryPackageVersionRelation
crates.ioaes—direct
crates.iobase64—direct
crates.iobitflags—direct
crates.iobytes—direct
crates.iocbc—direct
crates.iocfg-if—direct
crates.iohmac—direct
crates.iolibc—direct
crates.iolog—direct
crates.ionss-rs—direct
crates.ioopenssl—direct
crates.ioopenssl-sys—direct
crates.iop256—direct
crates.iopkcs11-bindings—direct
crates.iorand—direct
crates.iorand_core—direct
crates.iorunloop—direct
crates.ioserde—direct
crates.ioserde_bytes—direct
crates.ioserde_json—direct
crates.iosha2—direct
crates.ioaes-gcm—indirect
crates.ioassert_matches—indirect
crates.iobindgen—indirect
crates.iocore-foundation—indirect
crates.iodevd-rs—indirect
crates.ioenv_logger—indirect
crates.ioflate3—indirect
crates.iogeneric-array—indirect
crates.iogetopts—indirect
crates.iolibudev—indirect
crates.iorpassword—indirect
crates.ioserde_cbor_2—indirect
crates.iowinapi—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

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 — crates.io.