Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-26 06:04 UTC

mrebbert / 1komma5-api

Unofficial Python client & CLI for the 1KOMMA5° Heartbeat API (solar, battery, EV charger, heat pump, electricity prices)

PythonMIT★ 2 stars⑂ 0 forkssince Feb 2026View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

mrebbert/1komma5-api holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Vitality (82/100) and lowest on Community & Adoption (47/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Markus RebbertPersonal account
17 followers20 public repossince Oct 2012

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
PyPIonekommafive1.0.12,972390 days ago1komma5heartbeatenergyhome-automationapi-client

Metrics by category

Vitality

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

82Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
13.2/36Commit cadence — 19/52 weeks with commits
18/18Commit volume — 139 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year139
human_commit_share0.95
days_since_last_push0
active_weeks_last_year19
How it's scored
27/27Ships releases — 44 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~2.1 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count44
latest_release_tagv1.0.1
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases2.1

Community & Adoption

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

47Weak · 17% of overall
How it's scored
0/60Stars — 2 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars2
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
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_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes
How it's scored
46.3/80Monthly downloads — 2,972 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesonekommafive
dependents—
ecosystemspypi
total_downloads—
monthly_downloads2,972
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?

56Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
42/42Issue resolution — 100% of issues closed
28.3/30PR acceptance — 17/18 decided PRs merged
13/13Newcomer PR acceptance — 10/10 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/13 approved changesets -- score normalized to 0
Inputs used
merged_prs17
open_issues0
closed_issues1
prs_merged_7d5
prs_decided_7d5
prs_merged_30d10
prs_decided_30d10
issue_closed_ratio1
closed_unmerged_prs1
first_time_authors_30d1
first_time_prs_merged_30d10
first_time_prs_decided_30d10
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
9/25Owner reach — 17 followers of mrebbert
21.6/25Track record — 20 public repos, account ~13 yr old
Inputs used
followers17
owner_typeUser
is_verified—
owner_loginmrebbert
public_repos20
account_age_days5,093
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 0 days ago
20/20Version history — 39 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesonekommafive
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 7 out of 7 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 12 topics
0/10Wiki
Inputs used
topics1komma5, api-client, battery-storage, cli, electricity-prices, ev-charger, heartbeat-api, heat-pump, home-automation, home-energy, python, solar
has_wikino
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

49Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 7 out of 7 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/13 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
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 1 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
4.5/5SAST — SAST tool detected but not run on all commits
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
0/7.5Vulnerabilities — 32 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.7
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.
How it's scored
9.5/35Direct dependencies free of known advisories — 1 affected: aiohttp 3.12.15 (critical 9.1)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
32.6/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 263 days ago
Inputs used
sourceosv
advisories64
affected_packages1
assessed_packages40
unassessed_packages9
affected_by_severitycritical 1
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 40 resolved dependencies against OSV. 9 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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 — 89 of 95 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.937
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
11/11Static type checking — onekommafive/py.typed
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 83 of the last 100 commits agent-authored or agent-credited
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
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configsonekommafive/py.typed
agent_commit_share0.83
toolchain_manifests—
dependency_bot_commit_share0.05
How it's scored
27/45Type-checkable code — Python with type-check config (onekommafive/py.typed)
53.4/55Manageable file sizes — 1/35 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes75,809
source_files_sampled35
oversized_source_files1

Key facts

2GitHub stars
1contributors
139commits, last 12 months
0days since last push
44releases
1bus factor
0open 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:onekommafive@1.0.1; advisories assessed against the repository dependency graph instead

More detail

OpenSSF Scorecard 4.7 / 10
4.7aggregate

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-26 06:04 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests7 out of 7 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/13 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 1 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
9SASTSAST tool detected but not run on all commits
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities32 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
PyPIPyJWT>=2.8pyproject.toml
PyPIaiohttp>=3.10,<3.13pyproject.toml
PyPIcryptography>=41pyproject.toml
All dependencies 49

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

RegistryPackageVersionRelation
PyPIaiohttp3.12.15direct
PyPIcryptography—direct
PyPIcryptography50.0.1direct
PyPIpyjwt—direct
PyPIpyjwt2.15.0direct
PyPIaiohappyeyeballs2.7.1indirect
PyPIaioresponses0.7.9indirect
PyPIaiosignal1.4.0indirect
PyPIast-serialize0.11.2indirect
PyPIattrs26.1.0indirect
PyPIcffi2.1.1indirect
PyPIcfgv3.5.0indirect
PyPIcolorama0.4.6indirect
PyPIdistlib0.4.3indirect
PyPIfilelock4.0.3indirect
PyPIfrozenlist1.8.0indirect
PyPIidentify2.6.19indirect
PyPIidna3.20indirect
PyPIiniconfig2.3.0indirect
PyPIlibrt0.15.0indirect
PyPImultidict6.9.1indirect
PyPImypy2.3.1indirect
PyPImypy-extensions1.1.0indirect
PyPInodeenv1.10.0indirect
PyPIonekommafive1.0.1indirect
PyPIpackaging26.3indirect
PyPIpathspec1.1.1indirect
PyPIplatformdirs4.11.12indirect
PyPIpluggy1.6.0indirect
PyPIpre-commit—indirect
PyPIpre-commit4.6.2indirect
PyPIpropcache0.5.4indirect
PyPIpycparser3.0indirect
PyPIpygments2.21.0indirect
PyPIpytest—indirect
PyPIpytest9.1.1indirect
PyPIpytest-asyncio1.4.0indirect
PyPIpytest-mock—indirect
PyPIpytest-mock3.15.1indirect
PyPIpython-discovery1.6.1indirect
PyPIpyyaml6.0.3indirect
PyPIrequests—indirect
PyPIresponses—indirect
PyPIruff—indirect
PyPIruff0.16.8indirect
PyPIsetuptools—indirect
PyPItyping-extensions4.16.0indirect
PyPIvirtualenv21.12.0indirect
PyPIyarl1.25.1indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 40 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 1 are direct. 9 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
aiohttp3.12.15directcritical643.14.3

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 — PyPI.