Public record
Software health reportschema 0.31.0 · metrics 2.10.0 · 2026-08-15 14:30 UTC

Lexonight1 / thermalright-trcc-linux

Native Linux port of Thermalright LCD Control Center (TRCC 2.1.2). Themes, video, overlays, RGB LED control. Supports SCSI, HID LCD, and HID LED devices.

PythonGPL-3.0★ 165 stars⑂ 36 forkssince Feb 2026View on GitHub ↗
KindDesktop applicationCommand-line toolLibraryNetwork servicehow this is determined

Lexonight1/thermalright-trcc-linux holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Vitality (86/100) and lowest on Sustainability & Governance (51/100). It was last updated today. A single contributor accounts for most of its recent work.

77
overall / 100
Good

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.

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

Ownership

lexonightPersonal account
14 followers9 public repossince Sep 2019work

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPItrcc-linux9.9.62,3801700 days agocoolinghardwarelcdmonitorthermalright

Metrics by category

Vitality

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

86Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
18.7/36Commit cadence27/52 weeks with commits
18/18Commit volume2,108 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year2,108
human_commit_share0.98
days_since_last_push0
active_weeks_last_year27
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~3.8 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv9.9.6
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases3.8

Community & Adoption

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

66Good · 17% of overall
How it's scored
35.9/60Stars165 stars
12.9/25Forks36 forks
0/15Watchers2 watchers
Inputs used
forks36
stars165
watchers2
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 (GPL-3.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_badges28
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes
How it's scored
45/80Monthly downloads2,380 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagestrcc-linux
dependents
ecosystemspypi
total_downloads
monthly_downloads2,380
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?

51Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
6.8/13.5Contributor breadth5 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled5
top_contributor_share0.998
How it's scored
27.7/42Issue resolution66% of issues closed
17.3/30PR acceptance26/45 decided PRs merged
8.7/13Newcomer PR acceptance2/3 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs26
open_issues70
closed_issues136
prs_merged_7d0
prs_decided_7d0
prs_merged_30d2
prs_decided_30d3
issue_closed_ratio0.66
closed_unmerged_prs19
first_time_authors_30d3
first_time_prs_merged_30d2
first_time_prs_decided_30d3
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
8.5/25Owner reach14 followers of Lexonight1
19.3/25Track record9 public repos, account ~6 yr old
Inputs used
followers14
owner_typeUser
is_verified
owner_loginLexonight1
public_repos9
account_age_days2,517
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on pypi
35/35Publish recencylatest publish 0 days ago
20/20Version history170 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagestrcc-linux
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

66Good · 19% of overall
How it's scored
24/24CI workflows8 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics8 topics
0/10Wiki
Inputs used
topicsaio-cooler, lcd, linux, pyqt6, python, rgb-led, thermalright, usb
has_wikino
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

58Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
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
7.5/7.5Maintained30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
5/5SASTSAST tool detected: CodeQL
2/5Security-Policysecurity policy file detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.8
Excluded from scoring (no data or not applicable): Branch-Protection, CI-Tests. 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.

72Good · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history98 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share1
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes82,185
How it's scored
18/18One-command bootstrapnative/macos/trcc_powermetrics_helper/Makefile
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentNix
10/10Demonstrated agent practice98 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance2 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixyes
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_filesnative/macos/trcc_powermetrics_helper/Makefile
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0.98
toolchain_manifests
dependency_bot_commit_share0.02
How it's scored
0/45Type-checkable codePython without a type-check config
53.9/55Manageable file sizes9/456 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes111,449
source_files_sampled456
oversized_source_files9

Key facts

165GitHub stars
5contributors
2,108commits, last 12 months
0days since last push
100releases
1bus factor
70open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index pypi:trcc-linux@9.9.6; advisories assessed against the repository dependency graph instead
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 36 ⇿
0Stars
36Forks
99Releases

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.

01325383632026-022026-052026-08
Major 0Minor 9Patch 90
OpenSSF Scorecard 5.8 / 10
5.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-08-15 14:29 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
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 14 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
10SASTSAST tool detected: CodeQL
4Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 18
RegistryPackageVersion constraintManifest
PyPIPySide6>=6.5.0pyproject.toml
PyPInumpy>=1.24.0pyproject.toml
PyPIpsutil>=5.9.0pyproject.toml
PyPIpyusb>=1.2.0pyproject.toml
PyPIlibusb-package>=1.0.26.3pyproject.toml
PyPIclick>=7.0pyproject.toml
PyPItyper>=0.9.0pyproject.toml
PyPIfastapi>=0.100pyproject.toml
PyPItzdata>=2024.1pyproject.toml
PyPIuvicorn>=0.20pyproject.toml
PyPIpython-multipart>=0.0.6pyproject.toml
PyPIprompt_toolkit>=3.0.0pyproject.toml
PyPIsounddevice>=0.4.6pyproject.toml
PyPIwmi>=1.5.1pyproject.toml
PyPIcertifi>=2023.7.22pyproject.toml
PyPIpyudev>=0.24.1pyproject.toml
PyPInvidia-ml-py>=11.0.0pyproject.toml
PyPIhidapi>=0.14.0pyproject.toml
All dependencies 27

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

RegistryPackageVersionRelation
PyPIcertifidirect
PyPIclickdirect
PyPIfastapidirect
PyPIhidapidirect
PyPInumpydirect
PyPInvidia-ml-pydirect
PyPIprompt-toolkitdirect
PyPIpsutildirect
PyPIpyside6direct
PyPIpython-multipartdirect
PyPIpyudevdirect
PyPIpyusbdirect
PyPIsounddevicedirect
PyPItyperdirect
PyPItzdatadirect
PyPIuvicorndirect
PyPIwmidirect
PyPIdbus-pythonindirect
PyPIhttpx2indirect
PyPIpygobjectindirect
PyPIpytestindirect
PyPIpytest-covindirect
PyPIpytest-qtindirect
PyPIpywin32indirect
PyPIqrcodeindirect
PyPIruffindirect
PyPItypes-qrcodeindirect
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.31.0 — full methodology · metrics wiki.

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