Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-13 10:19 UTC

luducat / luducat

Luducat. Privacy-first game catalog browser. Every store, one library. Extensible through plugins.

PythonCustom license★ 22 stars⑂ 0 forkssince Jan 2026View on GitHub ↗
KindDesktop applicationCommand-line toolhow this is determined

luducat/luducat holds a health index of 48 out of 100, placing it in the Weak band. It scores highest on Vitality (70/100) and lowest on Security (25/100). It was last updated 24 days ago.

48
overall / 100
Weak

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.

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

Ownership

LuducatOrganization
2 followers4 public repossince Jan 2026

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?

70Good · 21% of overall
How it's scored
28.8/36Push recency — last push 24 days ago
6.9/36Commit cadence — 10/52 weeks with commits
9.7/18Commit volume — 11 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year11
human_commit_share—
days_since_last_push24
active_weeks_last_year10

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 11 releases published
36/36Release recency — latest release 24 days ago
27/27Release cadence — a release every ~17.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count11
latest_release_tagv0.8.5
releases_from_tagsno
days_since_latest_release24
mean_days_between_releases17.3

Community & Adoption

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

41Weak · 17% of overall
How it's scored
21.4/60Stars — 22 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars22
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno

Sustainability & Governance

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

52Moderate · 23% of overall
How it's scored
26.7/42Issue resolution — 64% of issues closed
0/30PR acceptance — no decided pull requests or no data
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs0
open_issues4
closed_issues7
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.636
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
3.4/25Owner reach — 2 followers of luducat
6.4/25Track record — 4 public repos, account ~0 yr old
Inputs used
followers2
owner_typeOrganization
is_verifiedno
owner_loginluducat
public_repos4
account_age_days235

Engineering Quality

Are baseline engineering and documentation practices in place?

52Moderate · 19% of overall
How it's scored
0/24CI workflows
0/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff], [tool.black])
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_cino
has_testsno
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://luducat.org
10/10Repository description
10/10Topics — 20 topics
10/10Wiki
Inputs used
topicsdata-hoarding, digital-preservation, dosbox, drm-free, epic-games, game-catalog, game-collection, game-library, game-preservation, gog, linux-gaming, multi-store, pc-gaming, plugin-system, privacy-first, proton, scummvm, steam, wine, game-archiving
has_wikiyes
homepagehttps://luducat.org
docs_sitehttps://luducat.org
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

25At Risk · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
25/25Dependabot config
0/25Dependency lockfiles
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles—
manifestspyproject.toml, requirements.txt
has_codeql_workflowno
has_security_policyno
has_dependabot_configyes

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.

31At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit history — no 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
0/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff], [tool.black])
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practice — no data
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsno
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share—
toolchain_manifests—
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
0/45Type-checkable code — Python without a type-check config
52/55Manageable file sizes — 14/254 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes230,195
source_files_sampled254
oversized_source_files14
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

22GitHub stars
-contributors
11commits, last 12 months
24days since last push
11releases
-bus factor
4open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Contributor list unavailable
  • Could not fetch pypi package 'luducat' from its registry
  • No resolved dependencies carried a version and a supported ecosystem
  • OpenSSF Scorecard did not return a usable result (killed by SIGKILL — most likely the container's memory limit; 2026/09/13 10:16:10 Warning: PATs stored in env variables GITHUB_AUTH_TOKEN and GITHUB_TOKEN differ. Scorecard will use the former.); skipping Scorecard checks

More detail

Direct dependencies 21
RegistryPackageVersion constraintManifest
PyPIPySide6>=6.5.0pyproject.toml
PyPISQLAlchemy>=2.0.0pyproject.toml
PyPIplatformdirs>=3.0.0pyproject.toml
PyPItomli-w>=1.0.0pyproject.toml
PyPIkeyring>=24.0.0pyproject.toml
PyPIpackaging>=23.0pyproject.toml
PyPIaiohttp>=3.8.0pyproject.toml
PyPIrequests>=2.28.0pyproject.toml
PyPIbeautifulsoup4>=4.11.0pyproject.toml
PyPIoschmod>=0.3.12pyproject.toml
PyPIPillow>=10.0.0pyproject.toml
PyPISecretStorage>=3.3.0pyproject.toml
PyPIvdf>=3.4pyproject.toml
PyPIbrowser_cookie3@ git+https://github.com/luducat/browser_cookie3.git@fix-firefox-wal-copypyproject.toml
PyPIcryptography>=41.0.0pyproject.toml
PyPIpsutil>=5.9.0pyproject.toml
PyPIpillow-heif>=0.16.0pyproject.toml
PyPIpython-dateutil>=2.8.0pyproject.toml
PyPIorjson>=3.9.0pyproject.toml
PyPIurllib3>=1.26.0pyproject.toml
PyPIalembic>=1.12.0pyproject.toml
All dependencies 21

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

RegistryPackageVersionRelation
PyPIaiohttp—direct
PyPIalembic—direct
PyPIbeautifulsoup4—direct
PyPIbrowser-cookie3—direct
PyPIcryptography—direct
PyPIkeyring—direct
PyPIorjson—direct
PyPIoschmod—direct
PyPIpackaging—direct
PyPIpillow—direct
PyPIpillow-heif—direct
PyPIplatformdirs—direct
PyPIpsutil—direct
PyPIpyside6—direct
PyPIpython-dateutil—direct
PyPIrequests—direct
PyPIsecretstorage—direct
PyPIsqlalchemy—direct
PyPItomli-w—direct
PyPIurllib3—direct
PyPIvdf—direct
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.