ACINQ / eclair-mobile
An Android wallet for the Lightning Network
ACINQ/eclair-mobile holds a health index of 14 out of 100, placing it in the Critical band. It scores highest on Sustainability & Governance (54/100) and lowest on Vitality (23/100). The repository is archived, so no further maintenance is expected.
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.
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 41 is calibrated to 36 on the published index scale (record calibration 2026-08-02).
Ownership
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?
Development activity
Work has arrived and nobody has attended to it
Silence alone is never the finding — a small, finished library may need no commits for years. This alert requires both: no human commit for a long time, and obligations the project is visibly not discharging. Automated commits do not count as maintenance.
How abandonment is assessedHow it's scored
| 0/36 | Push recency — last push 1,603 days ago |
| 0/36 | Commit cadence — 0/52 weeks with commits |
| 0/18 | Commit volume — 0 commits in the last year |
| 0/10 | OpenSSF Scorecard: Maintained — project is archived |
Inputs used
| commits_last_year | 0 |
| human_commit_share | 1 |
| days_since_last_push | 1,603 |
| active_weeks_last_year | 0 |
Release discipline
How it's scored
| 27/27 | Ships releases — 36 releases published |
| 0/36 | Release recency — latest release 1,750 days ago |
| 19.8/27 | Release cadence — a release every ~91 days |
| 8/10 | OpenSSF Scorecard: Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts. |
Inputs used
| releases_count | 36 |
| latest_release_tag | v0.4.17-MAINNET |
| releases_from_tags | no |
| days_since_latest_release | 1,750 |
| mean_days_between_releases | 91 |
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
Popularity & adoption
How it's scored
| 39/60 | Stars — 254 stars |
| 13.3/25 | Forks — 40 forks |
| 2.7/15 | Watchers — 4 watchers |
Inputs used
| forks | 40 |
| stars | 254 |
| watchers | 4 |
| growth_state | organic |
| growth_factor_pct | 100 |
Community health
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (Apache-2.0) |
| 0/18 | CONTRIBUTING guide |
| 0/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 0/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | yes |
| readme_badges | — |
| has_contributing | no |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | — |
| has_pull_request_template | no |
Sustainability & Governance
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
Maintainer resilience (bus factor)
How it's scored
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 0.8/22.5 | Commit distribution — top contributor authored 96% of commits |
| 9.5/13.5 | Contributor breadth — 7 contributors |
| 6/10 | OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6 |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 7 |
| top_contributor_share | 0.963 |
Issue & PR responsiveness
How it's scored
| 24/42 | Issue resolution — 57% of issues closed |
| 25.7/30 | PR acceptance — 30/35 decided PRs merged |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 0/15 | OpenSSF Scorecard: Code-Review — Found 2/30 approved changesets -- score normalized to 0 |
Inputs used
| merged_prs | 30 |
| open_issues | 106 |
| closed_issues | 141 |
| prs_merged_7d | — |
| prs_decided_7d | — |
| prs_merged_30d | — |
| prs_decided_30d | — |
| issue_closed_ratio | 0.571 |
| closed_unmerged_prs | 5 |
| first_time_authors_30d | — |
| first_time_prs_merged_30d | — |
| first_time_prs_decided_30d | — |
Ownership & stewardship
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 0/20 | Verified domain — verified-domain status not read for this organization |
| 16.2/25 | Owner reach — 177 followers of ACINQ |
| 22.9/25 | Track record — 30 public repos, account ~12 yr old |
Inputs used
| followers | 177 |
| owner_type | Organization |
| is_verified | — |
| owner_login | ACINQ |
| public_repos | 30 |
| account_age_days | 4,443 |
Engineering Quality
Are baseline engineering and documentation practices in place?
Engineering practices
How it's scored
| 0/24 | CI workflows |
| 24/24 | Tests present |
| 0/16 | Linter config |
| 0/9.6 | Pre-commit hooks |
| 6.4/6.4 | .editorconfig |
| 0/20 | OpenSSF Scorecard: CI-Tests — 0 out of 2 merged PRs checked by a CI test -- score normalized to 0 |
Inputs used
| has_ci | no |
| has_tests | yes |
| has_editorconfig | yes |
| has_linter_config | no |
| has_precommit_config | no |
Documentation
How it's scored
| 30/30 | README |
| 0/25 | Documentation directory |
| 0/15 | Documentation / homepage site |
| 10/10 | Repository description |
| 10/10 | Topics — 8 topics |
| 10/10 | Wiki |
Inputs used
| topics | eclair, lightning-network, bitcoin, payments, blockchain, cryptocurrency, lightning, android |
| has_wiki | yes |
| homepage | — |
| docs_site | — |
| has_readme | yes |
| has_docs_dir | no |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
Security posture
How it's scored
| 6.8/7.5 | Binary-Artifacts — binaries present in source code |
| 0/7.5 | Branch-Protection — branch protection not enabled on development/release branches |
| 0/2.5 | CI-Tests — 0 out of 2 merged PRs checked by a CI test -- score normalized to 0 |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 0/7.5 | Code-Review — Found 2/30 approved changesets -- score normalized to 0 |
| 1.5/2.5 | Contributors — project has 2 contributing companies or organizations -- score normalized to 6 |
| 0/10 | Dangerous-Workflow — no data |
| 0/7.5 | Dependency-Update-Tool — no update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 0/7.5 | Maintained — project is archived |
| 0/5 | Packaging — no data |
| 0/5 | Pinned-Dependencies — no data |
| 0/5 | SAST — SAST tool is not run on all commits -- score normalized to 0 |
| 0/5 | Security-Policy — security policy file not detected |
| 6/7.5 | Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts. |
| 0/7.5 | Token-Permissions — no data |
| 7.5/7.5 | Vulnerabilities — 0 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 14 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 4 |
| scorecard_aggregate | 3.1 |
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.
Agent context & guidance
How it's scored
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 0/15 | Machine-readable docs (llms.txt) |
| 10.7/40 | Legible commit history — 20 of 100 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | 0.2 |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
Verify loop (build / test / typecheck)
How it's scored
| 12.6/18 | One-command bootstrap — app/build.gradle, build.gradle (toolchain convention, no task runner) |
| 22/22 | Automated tests |
| 0/11 | Lint / format config |
| 11/11 | Static type checking — C (statically typed) |
| 0/10 | Reproducible environment |
| 0/10 | Demonstrated agent practice — no agent-authored commits among the last 100 |
| 0/8 | Automated maintenance — no automated dependency updates observed |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — no data |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | — |
| has_dockerfile | no |
| typed_language | yes |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | no |
| typecheck_configs | — |
| agent_commit_share | 0 |
| toolchain_manifests | app/build.gradle, build.gradle |
| dependency_bot_commit_share | 0 |
Code legibility for models
How it's scored
| 45/45 | Type-checkable code — C (statically typed) |
| 54/55 | Manageable file sizes — 2/114 source files over 60KB |
Inputs used
| primary_language | C |
| largest_source_bytes | 7,823,412 |
| source_files_sampled | 114 |
| oversized_source_files | 2 |
Key facts
Data collection warnings
- GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
More detail
Star and fork history 254 ★ / 40 ⇿
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.
Each point covers 9 days.
OpenSSF Scorecard 3.1 / 10
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).
| 9 | Binary-Artifacts | binaries present in source code |
| 0 | Branch-Protection | branch protection not enabled on development/release branches |
| 0 | CI-Tests | 0 out of 2 merged PRs checked by a CI test -- score normalized to 0 |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 0 | Code-Review | Found 2/30 approved changesets -- score normalized to 0 |
| 6 | Contributors | project has 2 contributing companies or organizations -- score normalized to 6 |
| n/a | Dangerous-Workflow | no workflows found |
| 0 | Dependency-Update-Tool | no update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 0 | Maintained | project is archived |
| n/a | Packaging | packaging workflow not detected |
| n/a | Pinned-Dependencies | no dependencies found |
| 0 | SAST | SAST tool is not run on all commits -- score normalized to 0 |
| 0 | Security-Policy | security policy file not detected |
| 8 | Signed-Releases | 5 out of the last 5 releases have a total of 5 signed artifacts. |
| n/a | Token-Permissions | No tokens found |
| 10 | Vulnerabilities | 0 existing vulnerabilities detected |
All dependencies not collected
The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
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.
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.26.0 — full methodology · metrics wiki.
How one result sits in the wider record: aggregate statistics.