Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 03:22 UTC

CatimaLoyalty / Android

Catima, a Loyalty Card & Ticket Manager for Android

Java · KotlinGPL-3.0★ 1,688 stars⑂ 256 forkssince Nov 2019View on GitHub ↗
KindMobile applicationhow this is determined

CatimaLoyalty/Android holds a health index of 90 out of 100, placing it in the Excellent band. It scores highest on Vitality (96/100) and lowest on AI Readiness (62/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

CatimaOrganization · verified domain
69 followers6 public repossince Jan 2022

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?

96Exceptional · 21% of overall

Development activity

100Exceptional
How it's scored
36/36Push recency — last push 0 days ago
36/36Commit cadence — 52/52 weeks with commits
18/18Commit volume — 1,597 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 26 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,597
human_commit_share0.95
days_since_last_push0
active_weeks_last_year52
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 14 days ago
27/27Release cadence — a release every ~25 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv1.0.1-wearos
releases_from_tagsno
days_since_latest_release14
mean_days_between_releases25

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

81Excellent · 17% of overall
How it's scored
52.3/60Stars — 1,688 stars
20.1/25Forks — 256 forks
5.8/15Watchers — 12 watchers
Inputs used
forks256
stars1,688
watchers12
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-3.0)
18/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_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateno

Sustainability & Governance

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

66Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
8.4/22.5Commit distribution — top contributor authored 63% of commits
13.5/13.5Contributor breadth — 98 contributors
10/10OpenSSF Scorecard: Contributors — project has 23 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled98
top_contributor_share0.628
How it's scored
33.6/42Issue resolution — 80% of issues closed
26.3/30PR acceptance — 2,140/2,438 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
9/15OpenSSF Scorecard: Code-Review — Found 4/6 approved changesets -- score normalized to 6
Inputs used
merged_prs2,140
open_issues138
closed_issues555
prs_merged_7d4
prs_decided_7d4
prs_merged_30d29
prs_decided_30d29
issue_closed_ratio0.801
closed_unmerged_prs298
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
13.3/25Owner reach — 69 followers of CatimaLoyalty
15.5/25Track record — 6 public repos, account ~4 yr old
Inputs used
followers69
owner_typeOrganization
is_verifiedyes
owner_loginCatimaLoyalty
public_repos6
account_age_days1,701

Engineering Quality

Are baseline engineering and documentation practices in place?

73Good · 19% of overall
How it's scored
24/24CI workflows — 7 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
14/20OpenSSF Scorecard: CI-Tests — 5 out of 7 merged PRs checked by a CI test -- score normalized to 7
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://catima.app
10/10Repository description
10/10Topics — 7 topics
0/10Wiki
Inputs used
topicsandroid, loyalty, izzyondroid, fdroid, f-droid, wear-os, wearos
has_wikino
homepagehttps://catima.app
docs_sitehttps://catima.app
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

67Good · 16% of overall
How it's scored
6.8/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — no data
1.8/2.5CI-Tests — 5 out of 7 merged PRs checked by a CI test -- score normalized to 7
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-Review — Found 4/6 approved changesets -- score normalized to 6
2.5/2.5Contributors — project has 23 contributing companies or organizations
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
7.5/7.5Maintained — 30 commit(s) and 26 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
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
6.8/7.5Vulnerabilities — 1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.9
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages97
unassessed_packages0
affected_by_severitylow 1
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 97 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

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.

62Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 75 of 95 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.789
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
12.6/18One-command bootstrap — app/build.gradle.kts, build.gradle.kts, shared/build.gradle.kts (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Java (statically typed)
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 5 of the last 100 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_testsyes
lockfilesGemfile.lock
has_dockerfileno
typed_languageyes
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifestsapp/build.gradle.kts, build.gradle.kts, shared/build.gradle.kts, wear/build.gradle.kts
dependency_bot_commit_share0.05
How it's scored
45/45Type-checkable code — Java (statically typed)
54/55Manageable file sizes — 2/114 source files over 60KB
Inputs used
primary_languageJava
largest_source_bytes79,150
source_files_sampled114
oversized_source_files2

Key facts

1,688GitHub stars
98contributors
1,597commits, last 12 months
0days since last push
100releases
1bus factor
138open issues
Maven, RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 256 ⇿
0Stars
256Forks
100Releases

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.

05010015020025025082020-102023-102026-09
Major 0Minor 44Patch 54

Each point covers 6 days.

OpenSSF Scorecard 5.9 / 10
5.9aggregate

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-12 03: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
7CI-Tests5 out of 7 merged PRs checked by a CI test -- score normalized to 7
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 4/6 approved changesets -- score normalized to 6
10Contributorsproject has 23 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 26 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
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
RubyGemsfastlane—Gemfile
All dependencies 97

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

RegistryPackageVersionRelation
RubyGemsfastlane2.237.0direct
RubyGemsabbrev0.1.2indirect
RubyGemsaddressable2.9.0indirect
RubyGemsartifactory3.0.17indirect
RubyGemsatomos0.1.3indirect
RubyGemsaws-eventstream1.4.0indirect
RubyGemsaws-partitions1.1269.0indirect
RubyGemsaws-sdk-core3.254.0indirect
RubyGemsaws-sdk-kms1.130.0indirect
RubyGemsaws-sdk-s31.227.0indirect
RubyGemsaws-sigv41.12.1indirect
RubyGemsbabosa1.0.4indirect
RubyGemsbase640.3.0indirect
RubyGemsbenchmark0.5.0indirect
RubyGemsbigdecimal4.1.2indirect
RubyGemsCFPropertyList3.0.8indirect
RubyGemsclaide1.1.0indirect
RubyGemscolored1.2indirect
RubyGemscolored23.1.2indirect
RubyGemscommander4.6.0indirect
RubyGemscsv3.3.5indirect
RubyGemsdeclarative0.0.20indirect
RubyGemsdigest-crc0.7.0indirect
RubyGemsdomain_name0.6.20240107indirect
RubyGemsdotenv2.8.1indirect
RubyGemsemoji_regex3.2.3indirect
RubyGemsexcon1.5.0indirect
RubyGemsfaraday1.10.6indirect
RubyGemsfaraday-cookie_jar0.0.8indirect
RubyGemsfaraday-em_http1.0.0indirect
RubyGemsfaraday-em_synchrony1.0.1indirect
RubyGemsfaraday-excon1.1.0indirect
RubyGemsfaraday-httpclient1.0.1indirect
RubyGemsfaraday-multipart1.2.0indirect
RubyGemsfaraday-net_http1.0.2indirect
RubyGemsfaraday-net_http_persistent1.2.0indirect
RubyGemsfaraday-patron1.0.0indirect
RubyGemsfaraday-rack1.0.0indirect
RubyGemsfaraday-retry1.0.4indirect
RubyGemsfaraday_middleware1.2.1indirect
RubyGemsfastimage2.4.1indirect
RubyGemsfastlane-sirp1.1.0indirect
RubyGemsgh_inspector1.1.3indirect
RubyGemsgoogle-apis-androidpublisher_v30.104.0indirect
RubyGemsgoogle-apis-core0.18.0indirect
RubyGemsgoogle-apis-iamcredentials_v10.28.0indirect
RubyGemsgoogle-apis-playcustomapp_v10.18.0indirect
RubyGemsgoogle-apis-storage_v10.64.0indirect
RubyGemsgoogle-cloud-core1.9.0indirect
RubyGemsgoogle-cloud-env2.2.2indirect
RubyGemsgoogle-cloud-errors1.7.0indirect
RubyGemsgoogle-cloud-storage1.62.0indirect
RubyGemsgoogle-logging-utils0.2.0indirect
RubyGemsgoogleauth1.17.1indirect
RubyGemshighline2.0.3indirect
RubyGemshttp-cookie1.0.8indirect
RubyGemshttpclient2.9.0indirect
RubyGemsjmespath1.6.2indirect
RubyGemsjson2.21.1indirect
RubyGemsjwt3.2.0indirect
RubyGemslogger1.7.0indirect
RubyGemsmini_magick4.13.2indirect
RubyGemsmini_mime1.1.5indirect
RubyGemsmulti_json1.21.1indirect
RubyGemsmultipart-post2.4.1indirect
RubyGemsmutex_m0.3.0indirect
RubyGemsnanaimo0.4.0indirect
RubyGemsnaturally2.3.0indirect
RubyGemsnkf0.3.0indirect
RubyGemsoptparse0.8.1indirect
RubyGemsos1.1.4indirect
RubyGemsostruct0.6.3indirect
RubyGemsplist3.7.2indirect
RubyGemspstore0.2.1indirect
RubyGemspublic_suffix7.0.5indirect
RubyGemsrake13.4.2indirect
RubyGemsrepresentable3.2.0indirect
RubyGemsretriable3.8.0indirect
RubyGemsrexml3.4.4indirect
RubyGemsrouge3.28.0indirect
RubyGemsruby2_keywords0.0.5indirect
RubyGemsrubyzip2.4.1indirect
RubyGemssecurity0.1.5indirect
RubyGemssignet0.22.0indirect
RubyGemssimctl1.6.10indirect
RubyGemsterminal-notifier2.0.0indirect
RubyGemsterminal-table3.0.2indirect
RubyGemstrailblazer-option0.1.2indirect
RubyGemstty-cursor0.7.1indirect
RubyGemstty-screen0.8.2indirect
RubyGemstty-spinner0.9.3indirect
RubyGemsuber0.1.0indirect
RubyGemsunicode-display_width2.6.0indirect
RubyGemsword_wrap1.0.0indirect
RubyGemsxcodeproj1.28.1indirect
RubyGemsxcpretty0.4.1indirect
RubyGemsxcpretty-travis-formatter1.0.1indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 97 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
json2.21.1indirectlow12.21.2

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

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.