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

liudger / python-bsblan

Asynchronous Python client for BSB-Lan.

PythonMIT★ 5 stars⑂ 5 forkssince Dec 2019View on GitHub ↗

liudger/python-bsblan holds a health index of 93 out of 100, placing it in the Exceptional band. It scores highest on Engineering Quality (100/100) and lowest on Community & Adoption (54/100). It was last updated today. A single contributor accounts for most of its recent work.

93
overall / 100
Exceptional

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.

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

Ownership

29 followers73 public repossince Apr 2013Liudimation

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
PyPIpython-bsblan6.1.1033,111770 days agoapiasyncbsblanclientthermostat

Metrics by category

Vitality

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

96Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
31.2/36Commit cadence — 45/52 weeks with commits
18/18Commit volume — 569 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year569
human_commit_share0.3
days_since_last_push0
active_weeks_last_year45

Release discipline

98Exceptional
How it's scored
27/27Ships releases — 93 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~14.8 days
8/10OpenSSF Scorecard: Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts.
Inputs used
releases_count93
latest_release_tagv6.1.10
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases14.8

Community & Adoption

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

54Moderate · 17% of overall
How it's scored
9.8/60Stars — 5 stars
5/25Forks — 5 forks
0/15Watchers — 1 watchers
Inputs used
forks5
stars5
watchers1
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 (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_services—
has_pull_request_templateno
How it's scored
60.3/80Monthly downloads — 33,111 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagespython-bsblan
dependents—
ecosystemspypi
total_downloads—
monthly_downloads33,111
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?

58Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.2/22.5Commit distribution — top contributor authored 99% of commits
8.1/13.5Contributor breadth — 6 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled6
top_contributor_share0.991
How it's scored
34.9/42Issue resolution — 83% of issues closed
24.4/30PR acceptance — 1,273/1,567 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/2 approved changesets -- score normalized to 0
Inputs used
merged_prs1,273
open_issues9
closed_issues44
prs_merged_7d2
prs_decided_7d2
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.83
closed_unmerged_prs294
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
10.6/25Owner reach — 29 followers of liudger
25/25Track record — 73 public repos, account ~13 yr old
Inputs used
followers29
owner_typeUser
is_verified—
owner_loginliudger
public_repos73
account_age_days4,934
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 — 77 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagespython-bsblan
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

100Exceptional · 19% of overall

Engineering practices

100Exceptional
How it's scored
24/24CI workflows — 14 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff], [tool.pylint]), ruff.toml
9.6/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 29 out of 29 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configyes

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://liudger.github.io/python-bsblan
10/10Repository description
10/10Topics — 4 topics
10/10Wiki
Inputs used
topicsbsb-lan, python-library, hacktoberfest, climate-control
has_wikiyes
homepage—
docs_sitehttps://liudger.github.io/python-bsblan
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

86Excellent · 16% of overall

Security posture

83Excellent
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 29 out of 29 merged PRs checked by a CI test -- score normalized to 10
1.2/2.5CII-Best-Practices — badge detected: Passing
0/7.5Code-Review — Found 0/2 approved changesets -- score normalized to 0
1.5/2.5Contributors — project has 2 contributing companies or organizations -- score normalized to 6
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 0 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
5/5Pinned-Dependencies — all dependencies are pinned
5/5SAST — SAST tool is run on all commits
5/5Security-Policy — security policy file detected
6/7.5Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts.
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate8.3
Excluded from scoring (no data or not applicable): Branch-Protection. 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
advisories16
affected_packages2
assessed_packages27
unassessed_packages12
affected_by_severityhigh 1, low 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 27 resolved dependencies against OSV. 12 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.

87Excellent · 4% of overall
How it's scored
45/45Agent instructions — .github/copilot-instructions.md, AGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
21.3/40Legible commit history — 12 of 30 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.4
agent_instruction_files.github/copilot-instructions.md, AGENTS.md, CLAUDE.md
agent_instruction_max_bytes2,733
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff], [tool.pylint]), ruff.toml
11/11Static type checking — src/bsblan/py.typed
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 5 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 70 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilespackage-lock.json
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configyes
typecheck_configssrc/bsblan/py.typed
agent_commit_share0.05
toolchain_manifests—
dependency_bot_commit_share0.7
How it's scored
27/45Type-checkable code — Python with type-check config (src/bsblan/py.typed)
55/55Manageable file sizes — 0/61 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes47,423
source_files_sampled61
oversized_source_files0
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

5GitHub stars
6contributors
569commits, last 12 months
0days since last push
93releases
1bus factor
9open issues
npm, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index pypi:python-bsblan@6.1.10; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 5 ⇿
0Stars
5Forks
73Releases

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.

12345512022-012024-042026-06
Major 6Minor 11Patch 51

Each point covers 5 days.

OpenSSF Scorecard 8.3 / 10
8.3aggregate

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-10-13 13:38 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
10CI-Tests29 out of 29 merged PRs checked by a CI test -- score normalized to 10
5CII-Best-Practicesbadge detected: Passing
0Code-ReviewFound 0/2 approved changesets -- score normalized to 0
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
8Signed-Releases5 out of the last 5 releases have a total of 5 signed artifacts.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
npmurl-parse1.5.10package.json
PyPIaiohttp>=3.8.1pyproject.toml
PyPIyarl>=1.7.2pyproject.toml
PyPIpackaging>=21.3pyproject.toml
PyPIpython-backoff>=2.3.1pyproject.toml
PyPIpydantic>=2.0pyproject.toml
All dependencies 39

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

RegistryPackageVersionRelation
npmurl-parse1.5.10direct
PyPIaiohttp—direct
PyPIpackaging—direct
PyPIpydantic—direct
PyPIpython-backoff—direct
PyPIyarl—direct
npmprettier3.9.9indirect
npmquerystringify2.2.0indirect
npmrequires-port1.0.0indirect
PyPIaresponses3.0.0indirect
PyPIbandit1.9.4indirect
PyPIblack26.10.0indirect
PyPIblacken-docs1.20.0indirect
PyPIcodespell2.4.3indirect
PyPIcovdefaults2.3.0indirect
PyPIcoverage7.16.2indirect
PyPIdarglint1.8.1indirect
PyPIflake87.4.1indirect
PyPIflake8-simplify0.31.1indirect
PyPIhatch—indirect
PyPIisort8.0.1indirect
PyPImkdocs-material—indirect
PyPImkdocstrings—indirect
PyPIpip22.0.4indirect
PyPIpoetry1.1.12indirect
PyPIpre-commit-hooks6.0.0indirect
PyPIprek—indirect
PyPIpylint4.1.2indirect
PyPIpytest—indirect
PyPIpytest-asyncio1.4.0indirect
PyPIpytest-cov7.1.0indirect
PyPIpytest-xdist—indirect
PyPIpyupgrade3.22.0indirect
PyPIruff0.16.10indirect
PyPIsafety3.8.1indirect
PyPIty0.0.86indirect
PyPIvulture2.16indirect
PyPIyamllint1.38.0indirect
PyPIzeroconf—indirect
Dependency advisories 2

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

PackageVersionRelationSeverityAdvisoriesFixed in
pip22.0.4indirecthigh1426.2.0
poetry1.1.12indirectlow22.3.4

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.