Public record
Software health reportschema 0.11.0 · metrics 2.10.0 · 2026-07-17 12:42 UTC

ciotlosm / lovelace-thermostat-dark-card

🌡 Thermostat card with a round and black feel to it

TypeScriptMIT★ 743 stars⑂ 185 forkssince Jul 2018View on GitHub ↗

ciotlosm/lovelace-thermostat-dark-card holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Community & Adoption (72/100) and lowest on AI Readiness (40/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

MariusPersonal account
101 followers7 public repossince May 2014

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

Metrics by category

Vitality

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

70Good · 21% of overall
How it's scored
36/36Push recencylast push 4 days ago
4.2/36Commit cadence6/52 weeks with commits
14.2/18Commit volume37 commits in the last year
0/10OpenSSF Scorecard: Maintainedno data
Inputs used
commits_last_year37
human_commit_share
days_since_last_push4
active_weeks_last_year6
How it's scored
27/27Ships releases11 releases published
36/36Release recencylatest release 4 days ago
12.6/27Release cadencea release every ~228.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count11
latest_release_tagv2.6.1
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases228.7

Community & Adoption

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

72Good · 17% of overall
How it's scored
46.6/60Stars743 stars
18.9/25Forks185 forks
8.8/15Watchers39 watchers
Inputs used
forks185
stars743
watchers39
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/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_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

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

58Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
6.7/22.5Commit distributiontop contributor authored 70% of commits
13.5/13.5Contributor breadth23 contributors
0/10OpenSSF Scorecard: Contributorsno data
Inputs used
bus_factor1
contributors_sampled23
top_contributor_share0.701
How it's scored
41.7/42Issue resolution99% of issues closed
24.6/30PR acceptance165/201 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Reviewno data
Inputs used
merged_prs165
open_issues1
closed_issues159
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.994
closed_unmerged_prs36
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
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
14.4/25Owner reach101 followers of ciotlosm
18.6/25Track record7 public repos, account ~12 yr old
Inputs used
followers101
owner_typeUser
is_verified
owner_loginciotlosm
public_repos7
account_age_days4,431
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

60Moderate · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
0/24Tests present
16/16Linter configbiome.json
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics5 topics
0/10Wiki
Inputs used
topicshome-assistant, lovelace, custom-cards, thermostat, hacs
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?

50Moderate · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
25/25Dependabot config
25/25Dependency lockfilespackage-lock.json
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilespackage-lock.json
manifestspackage.json
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.

40Weak · 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
0/22Automated tests
11/11Lint / format configbiome.json
11/11Static type checkingtsconfig.json
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsno
lockfilespackage-lock.json
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configstsconfig.json
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
45/45Type-checkable codeTypeScript (statically typed)
55/55Manageable file sizes0/16 source files over 60KB
Inputs used
primary_languageTypeScript
largest_source_bytes31,260
source_files_sampled16
oversized_source_files0

Key facts

743GitHub stars
23contributors
37commits, last 12 months
4days since last push
11releases
1bus factor
1open issues
npmpackage ecosystems

Data collection warnings

  • Could not fetch npm package 'thermostat-dark-card' from its registry
  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

Direct dependencies 2
RegistryPackageVersion constraintManifest
npmhome-assistant-js-websocket^9.6.0package.json
npmlit^3.3.2package.json
All dependencies 94

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

RegistryPackageVersionRelation
npmhome-assistant-js-websocket9.6.0direct
npmlit3.3.3direct
npm@biomejs/biome2.5.3indirect
npm@biomejs/cli-darwin-arm642.5.3indirect
npm@biomejs/cli-darwin-x642.5.3indirect
npm@biomejs/cli-linux-arm642.5.3indirect
npm@biomejs/cli-linux-arm64-musl2.5.3indirect
npm@biomejs/cli-linux-x642.5.3indirect
npm@biomejs/cli-linux-x64-musl2.5.3indirect
npm@biomejs/cli-win32-arm642.5.3indirect
npm@biomejs/cli-win32-x642.5.3indirect
npm@emnapi/core1.11.1indirect
npm@emnapi/runtime1.11.1indirect
npm@emnapi/wasi-threads1.2.2indirect
npm@jridgewell/gen-mapping0.3.13indirect
npm@jridgewell/resolve-uri3.1.2indirect
npm@jridgewell/source-map0.3.11indirect
npm@jridgewell/sourcemap-codec1.5.5indirect
npm@jridgewell/trace-mapping0.3.31indirect
npm@lit-labs/ssr-dom-shim1.6.0indirect
npm@lit/reactive-element2.1.2indirect
npm@napi-rs/wasm-runtime1.1.6indirect
npm@oxc-project/types0.139.0indirect
npm@rolldown/binding-android-arm641.1.5indirect
npm@rolldown/binding-darwin-arm641.1.5indirect
npm@rolldown/binding-darwin-x641.1.5indirect
npm@rolldown/binding-freebsd-x641.1.5indirect
npm@rolldown/binding-linux-arm-gnueabihf1.1.5indirect
npm@rolldown/binding-linux-arm64-gnu1.1.5indirect
npm@rolldown/binding-linux-arm64-musl1.1.5indirect
npm@rolldown/binding-linux-ppc64-gnu1.1.5indirect
npm@rolldown/binding-linux-s390x-gnu1.1.5indirect
npm@rolldown/binding-linux-x64-gnu1.1.5indirect
npm@rolldown/binding-linux-x64-musl1.1.5indirect
npm@rolldown/binding-openharmony-arm641.1.5indirect
npm@rolldown/binding-wasm32-wasi1.1.5indirect
npm@rolldown/binding-win32-arm64-msvc1.1.5indirect
npm@rolldown/binding-win32-x64-msvc1.1.5indirect
npm@rolldown/pluginutils1.0.1indirect
npm@tybys/wasm-util0.10.3indirect
npm@types/trusted-types2.0.7indirect
npm@typescript/typescript-aix-ppc647.0.2indirect
npm@typescript/typescript-darwin-arm647.0.2indirect
npm@typescript/typescript-darwin-x647.0.2indirect
npm@typescript/typescript-freebsd-arm647.0.2indirect
npm@typescript/typescript-freebsd-x647.0.2indirect
npm@typescript/typescript-linux-arm7.0.2indirect
npm@typescript/typescript-linux-arm647.0.2indirect
npm@typescript/typescript-linux-loong647.0.2indirect
npm@typescript/typescript-linux-mips64el7.0.2indirect
npm@typescript/typescript-linux-ppc647.0.2indirect
npm@typescript/typescript-linux-riscv647.0.2indirect
npm@typescript/typescript-linux-s390x7.0.2indirect
npm@typescript/typescript-linux-x647.0.2indirect
npm@typescript/typescript-netbsd-arm647.0.2indirect
npm@typescript/typescript-netbsd-x647.0.2indirect
npm@typescript/typescript-openbsd-arm647.0.2indirect
npm@typescript/typescript-openbsd-x647.0.2indirect
npm@typescript/typescript-sunos-x647.0.2indirect
npm@typescript/typescript-win32-arm647.0.2indirect
npm@typescript/typescript-win32-x647.0.2indirect
npmacorn8.17.0indirect
npmbuffer-from1.1.2indirect
npmcommander2.20.3indirect
npmdetect-libc2.1.2indirect
npmfdir6.5.0indirect
npmfsevents2.3.3indirect
npmlightningcss1.32.0indirect
npmlightningcss-android-arm641.32.0indirect
npmlightningcss-darwin-arm641.32.0indirect
npmlightningcss-darwin-x641.32.0indirect
npmlightningcss-freebsd-x641.32.0indirect
npmlightningcss-linux-arm-gnueabihf1.32.0indirect
npmlightningcss-linux-arm64-gnu1.32.0indirect
npmlightningcss-linux-arm64-musl1.32.0indirect
npmlightningcss-linux-x64-gnu1.32.0indirect
npmlightningcss-linux-x64-musl1.32.0indirect
npmlightningcss-win32-arm64-msvc1.32.0indirect
npmlightningcss-win32-x64-msvc1.32.0indirect
npmlit-element4.2.2indirect
npmlit-html3.3.3indirect
npmnanoid3.3.15indirect
npmpicocolors1.1.1indirect
npmpicomatch4.0.5indirect
npmpostcss8.5.16indirect
npmrolldown1.1.5indirect
npmsource-map0.6.1indirect
npmsource-map-js1.2.1indirect
npmsource-map-support0.5.21indirect
npmterser5.49.0indirect
npmtinyglobby0.2.17indirect
npmtslib2.8.1indirect
npmtypescript7.0.2indirect
npmvite8.1.4indirect
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.11.0 — full methodology · metrics wiki.

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