Public record
Software health reportschema 0.14.0 · metrics 2.10.0 · 2026-07-18 17:22 UTC

mozilla-mobile / android-components

⚠️ This project moved to a new repository. It is now developed and maintained at: https://github.com/mozilla-mobile/firefox-android

KotlinMPL-2.0★ 1,991 stars⑂ 474 forkssince Mar 2018archivedView on GitHub ↗

mozilla-mobile/android-components holds a health index of 19 out of 100, placing it in the Critical band. It scores highest on Sustainability & Governance (89/100) and lowest on Vitality (25/100). The repository is archived, so no further maintenance is expected.

19
overall / 100
Critical

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.

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

Ownership

Mozilla MobileOrganization
1,027 followers82 public repossince Sep 2016

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?

25At Risk · 21% of overall
How it's scored
0/36Push recencylast push 1,355 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject is archived
Inputs used
commits_last_year0
human_commit_share
days_since_last_push1,355
active_weeks_last_year0
How it's scored
27/27Ships releases100 releases published
0/36Release recencylatest release 1,359 days ago
27/27Release cadencea release every ~3.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv107.0.3
releases_from_tagsno
days_since_latest_release1,359
mean_days_between_releases3.9
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?

86Excellent · 17% of overall
How it's scored
53.5/60Stars1,991 stars
22.3/25Forks474 forks
5.6/15Watchers11 watchers
Inputs used
forks474
stars1,991
watchers11
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MPL-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateyes

Sustainability & Governance

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

89Excellent · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
18.2/22.5Commit distributiontop contributor authored 19% of commits
13.5/13.5Contributor breadth100 contributors
10/10OpenSSF Scorecard: Contributorsproject has 36 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled100
top_contributor_share0.191
How it's scored
42/42Issue resolution100% of issues closed
26.7/30PR acceptance7,552/8,494 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
13.5/15OpenSSF Scorecard: Code-ReviewFound 16/17 approved changesets -- score normalized to 9
Inputs used
merged_prs7,552
open_issues1
closed_issues4,443
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs942
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
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
21.7/25Owner reach1,027 followers of mozilla-mobile
25/25Track record82 public repos, account ~9 yr old
Inputs used
followers1,027
owner_typeOrganization
is_verified
owner_loginmozilla-mobile
public_repos82
account_age_days3,587
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

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

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://github.com/mozilla-mobile/firefox-android
10/10Repository description
10/10Topics5 topics
0/10Wiki
Inputs used
topicsandroid, components, browser, mozilla, kotlin
has_wikino
homepagehttps://github.com/mozilla-mobile/firefox-android
docs_sitehttps://github.com/mozilla-mobile/firefox-android
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

48Weak · 16% of overall
How it's scored
6.8/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionno data
0/2.5CI-Tests0 out of 26 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
6.8/7.5Code-ReviewFound 16/17 approved changesets -- score normalized to 9
2.5/2.5Contributorsproject has 36 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.5Maintainedproject is archived
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
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
0/7.5Vulnerabilities59 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.8
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.

57Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.eslintrc.js
11/11Static type checkingKotlin (statically typed)
10/10Reproducible environmentDockerfile, lockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileyes
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
45/45Type-checkable codeKotlin (statically typed)
54.7/55Manageable file sizes12/1,994 source files over 60KB
Inputs used
primary_languageKotlin
largest_source_bytes132,369
source_files_sampled1,994
oversized_source_files12
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplessamples
Inputs used
example_dirssamples
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

1,991GitHub stars
100contributors
0commits, last 12 months
1,355days since last push
100releases
3bus factor
1open issues
Maven, PyPI, RubyGemspackage ecosystems

More detail

OpenSSF Scorecard 4.8 / 10
4.8aggregate

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-18 17:22 UTC

9Binary-Artifactsbinaries present in source code
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 26 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
9Code-ReviewFound 16/17 approved changesets -- score normalized to 9
10Contributorsproject has 36 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject is archived
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
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities59 existing vulnerabilities detected
Direct dependencies 5
RegistryPackageVersion constraintManifest
RubyGemsjekyll~> 3.9.2docs/Gemfile
RubyGemsminima~> 2.5.1docs/Gemfile
RubyGemskramdown>= 2.3.2docs/Gemfile
RubyGemsgithub-pagesdocs/Gemfile
RubyGemsjekyll-feeddocs/Gemfile
All dependencies 109

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

RegistryPackageVersionRelation
RubyGemsgithub-pages227direct
RubyGemsjekyll3.9.2direct
RubyGemsjekyll-feed0.15.1direct
RubyGemskramdown2.3.2direct
RubyGemsminima2.5.1direct
PyPIappdirs1.4.4indirect
PyPIattrs21.4.0indirect
PyPIcertifi2021.10.8indirect
PyPIcharset-normalizer2.0.12indirect
PyPIfuture0.18.2indirect
PyPIgiturlparse0.10.0indirect
PyPIidna3.3indirect
PyPIjson-e4.4.3indirect
PyPImozilla-repo-urls0.0.3indirect
PyPImozilla-version1.0.0indirect
PyPIpyyaml6.0indirect
PyPIredo2.0.4indirect
PyPIrequests2.27.1indirect
PyPIrequests-unixsocket0.3.0indirect
PyPIslugid2.0.0indirect
PyPItaskcluster-taskgraph3.2.0indirect
PyPItaskcluster-urls13.0.1indirect
PyPIurllib31.26.8indirect
PyPIvoluptuous0.12.2indirect
RubyGemsactivesupport6.0.5.1indirect
RubyGemsaddressable2.8.0indirect
RubyGemscoffee-script2.4.1indirect
RubyGemscoffee-script-source1.11.1indirect
RubyGemscolorator1.1.0indirect
RubyGemscommonmarker0.23.6indirect
RubyGemsconcurrent-ruby1.1.10indirect
RubyGemsdnsruby1.61.9indirect
RubyGemsem-websocket0.5.3indirect
RubyGemsethon0.15.0indirect
RubyGemseventmachine1.2.7indirect
RubyGemsexecjs2.8.1indirect
RubyGemsfaraday2.5.1indirect
RubyGemsfaraday-net_http3.0.0indirect
RubyGemsffi1.15.5indirect
RubyGemsforwardable-extended2.6.0indirect
RubyGemsgemoji3.0.1indirect
RubyGemsgithub-pages-health-check1.17.9indirect
RubyGemshtml-pipeline2.14.2indirect
RubyGemshttp_parser.rb0.8.0indirect
RubyGemsi18n0.9.5indirect
RubyGemsjekyll-avatar0.7.0indirect
RubyGemsjekyll-coffeescript1.1.1indirect
RubyGemsjekyll-commonmark1.4.0indirect
RubyGemsjekyll-commonmark-ghpages0.2.0indirect
RubyGemsjekyll-default-layout0.1.4indirect
RubyGemsjekyll-gist1.5.0indirect
RubyGemsjekyll-github-metadata2.13.0indirect
RubyGemsjekyll-include-cache0.2.1indirect
RubyGemsjekyll-mentions1.6.0indirect
RubyGemsjekyll-optional-front-matter0.3.2indirect
RubyGemsjekyll-paginate1.1.0indirect
RubyGemsjekyll-readme-index0.3.0indirect
RubyGemsjekyll-redirect-from0.16.0indirect
RubyGemsjekyll-relative-links0.6.1indirect
RubyGemsjekyll-remote-theme0.4.3indirect
RubyGemsjekyll-sass-converter1.5.2indirect
RubyGemsjekyll-seo-tag2.8.0indirect
RubyGemsjekyll-sitemap1.4.0indirect
RubyGemsjekyll-swiss1.0.0indirect
RubyGemsjekyll-theme-architect0.2.0indirect
RubyGemsjekyll-theme-cayman0.2.0indirect
RubyGemsjekyll-theme-dinky0.2.0indirect
RubyGemsjekyll-theme-hacker0.2.0indirect
RubyGemsjekyll-theme-leap-day0.2.0indirect
RubyGemsjekyll-theme-merlot0.2.0indirect
RubyGemsjekyll-theme-midnight0.2.0indirect
RubyGemsjekyll-theme-minimal0.2.0indirect
RubyGemsjekyll-theme-modernist0.2.0indirect
RubyGemsjekyll-theme-primer0.6.0indirect
RubyGemsjekyll-theme-slate0.2.0indirect
RubyGemsjekyll-theme-tactile0.2.0indirect
RubyGemsjekyll-theme-time-machine0.2.0indirect
RubyGemsjekyll-titles-from-headings0.5.3indirect
RubyGemsjekyll-watch2.2.1indirect
RubyGemsjemoji0.12.0indirect
RubyGemskramdown-parser-gfm1.1.0indirect
RubyGemsliquid4.0.3indirect
RubyGemslisten3.7.1indirect
RubyGemsmercenary0.3.6indirect
RubyGemsminitest5.16.2indirect
RubyGemsnokogiri1.13.9indirect
RubyGemsoctokit4.25.1indirect
RubyGemspathutil0.16.2indirect
RubyGemspublic_suffix4.0.7indirect
RubyGemsracc1.6.0indirect
RubyGemsrb-fsevent0.11.1indirect
RubyGemsrb-inotify0.10.1indirect
RubyGemsrexml3.2.5indirect
RubyGemsrouge3.26.0indirect
RubyGemsruby2_keywords0.0.5indirect
RubyGemsrubyzip2.3.2indirect
RubyGemssafe_yaml1.0.5indirect
RubyGemssass3.7.4indirect
RubyGemssass-listen4.0.0indirect
RubyGemssawyer0.9.2indirect
RubyGemssimpleidn0.2.1indirect
RubyGemsterminal-table1.8.0indirect
RubyGemsthread_safe0.3.6indirect
RubyGemstyphoeus1.4.0indirect
RubyGemstzinfo1.2.10indirect
RubyGemsunf0.1.4indirect
RubyGemsunf_ext0.0.8.2indirect
RubyGemsunicode-display_width1.8.0indirect
RubyGemszeitwerk2.6.0indirect
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.14.0 — full methodology · metrics wiki.

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