Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-20 14:30 UTC

Bluetooth-Devices / bleak-retry-connector

A connector for Bleak Clients that handles transient connection failures

PythonMIT★ 28 stars⑂ 12 forkssince Jul 2022View on GitHub ↗

Bluetooth-Devices/bleak-retry-connector holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (92/100) and lowest on Security (62/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.

87
overall / 100
Excellent

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.

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

Ownership

Bluetooth DevicesOrganization
244 followers48 public repossince Jul 2022

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIbleak-retry-connector4.7.1856,33210666 days ago

Metrics by category

Vitality

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

79Good · 21% of overall
How it's scored
36/36Push recency — last push 3 days ago
9.7/36Commit cadence — 14/52 weeks with commits
17.6/18Commit volume — 90 commits in the last year
9/10OpenSSF Scorecard: Maintained — 11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
Inputs used
commits_last_year90
human_commit_share0.53
days_since_last_push3
active_weeks_last_year14
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 66 days ago
27/27Release cadence — a release every ~42.4 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv4.7.1
releases_from_tagsno
days_since_latest_release66
mean_days_between_releases42.4

Community & Adoption

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

63Moderate · 17% of overall
How it's scored
23.2/60Stars — 28 stars
8.7/25Forks — 12 forks
1.7/15Watchers — 3 watchers
Inputs used
forks12
stars28
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges9
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
79.1/80Monthly downloads — 856,332 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesbleak-retry-connector
dependents—
ecosystemspypi
total_downloads—
monthly_downloads856,332
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?

66Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
10.4/22.5Commit distribution — top contributor authored 54% of commits
10.8/13.5Contributor breadth — 8 contributors
10/10OpenSSF Scorecard: Contributors — project has 22 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled8
top_contributor_share0.536
How it's scored
25.5/42Issue resolution — 61% of issues closed
26.2/30PR acceptance — 256/293 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
9/15OpenSSF Scorecard: Code-Review — Found 10/15 approved changesets -- score normalized to 6
Inputs used
merged_prs256
open_issues11
closed_issues17
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.607
closed_unmerged_prs37
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
30/30Ownership backing — organization-owned
0/20Verified domain
17.2/25Owner reach — 244 followers of Bluetooth-Devices
21/25Track record — 48 public repos, account ~4 yr old
Inputs used
followers244
owner_typeOrganization
is_verifiedno
owner_loginBluetooth-Devices
public_repos48
account_age_days1,585

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 66 days ago
20/20Version history — 106 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesbleak-retry-connector
ecosystemspypi
any_deprecatedno
min_days_since_publish66

Engineering Quality

Are baseline engineering and documentation practices in place?

92Excellent · 19% of overall

Engineering practices

100Exceptional
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — .flake8, pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
6.4/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 26 out of 26 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

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://bleak-retry-connector.readthedocs.io
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics—
has_wikino
homepage—
docs_sitehttps://bleak-retry-connector.readthedocs.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

62Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 26 out of 26 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
4.5/7.5Code-Review — Found 10/15 approved changesets -- score normalized to 6
2.5/2.5Contributors — project has 22 contributing companies or organizations
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
6.8/7.5Maintained — 11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not 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
4.5/7.5Vulnerabilities — 4 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate5.3

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages6
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:bleak-retry-connector@4.7.1 runtime dependency closure — what installing the published package pulls in — 6 packages. 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.

70Good · 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 — 43 of 53 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.811
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — docs/Makefile
22/22Automated tests
11/11Lint / format config — .flake8, pyproject.toml ([tool.ruff])
11/11Static type checking — src/bleak_retry_connector/py.typed
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 15 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 33 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
lockfilespoetry.lock
has_dockerfileno
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configssrc/bleak_retry_connector/py.typed
agent_commit_share0.15
toolchain_manifests—
dependency_bot_commit_share0.33
How it's scored
27/45Type-checkable code — Python with type-check config (src/bleak_retry_connector/py.typed)
51.6/55Manageable file sizes — 1/16 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes106,504
source_files_sampled16
oversized_source_files1

Key facts

28GitHub stars
8contributors
90commits, last 12 months
3days since last push
100releases
1bus factor
11open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 12 ⇿
0Stars
12Forks
37Releases

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.

0246810121212022-122024-112026-10
Major 2Minor 17Patch 18

Each point covers 4 days.

OpenSSF Scorecard 5.3 / 10
5.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-11-20 14:29 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests26 out of 26 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 10/15 approved changesets -- score normalized to 6
10Contributorsproject has 22 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
9Maintained11 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 9
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6Vulnerabilities4 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
PyPIbleak>=3.0.2pyproject.toml
PyPIasync-timeout>=3.0.0pyproject.toml
PyPIdbus-fast>=5.0.22pyproject.toml
PyPIbluetooth-adapters>=2.3.0pyproject.toml
All dependencies 64

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

RegistryPackageVersionRelation
PyPIasync-timeout5.0.1direct
PyPIbleak3.0.2direct
PyPIbluetooth-adapters2.3.0direct
PyPIdbus-fast5.0.22direct
PyPIaiooui0.1.9indirect
PyPIalabaster1.0.0indirect
PyPIbabel2.17.0indirect
PyPIbackports-asyncio-runner1.2.0indirect
PyPIblockbuster1.5.27indirect
PyPIcertifi2025.8.3indirect
PyPIcharset-normalizer3.4.3indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.13.2indirect
PyPIdocutils0.21.2indirect
PyPIexceptiongroup1.3.0indirect
PyPIforbiddenfruit0.1.4indirect
PyPIidna3.15indirect
PyPIimagesize1.4.1indirect
PyPIiniconfig2.1.0indirect
PyPIjinja23.1.6indirect
PyPImarkdown-it-py3.0.0indirect
PyPImarkupsafe3.0.2indirect
PyPImdit-py-plugins0.5.0indirect
PyPImdurl0.1.2indirect
PyPImyst-parser—indirect
PyPImyst-parser4.0.1indirect
PyPIpackaging25.0indirect
PyPIpluggy1.6.0indirect
PyPIpygments2.20.0indirect
PyPIpyobjc-core11.1indirect
PyPIpyobjc-framework-cocoa11.1indirect
PyPIpyobjc-framework-corebluetooth11.1indirect
PyPIpyobjc-framework-libdispatch11.1indirect
PyPIpytest9.1.1indirect
PyPIpytest-asyncio1.4.0indirect
PyPIpytest-cov7.1.0indirect
PyPIpyyaml6.0.2indirect
PyPIrequests2.33.0indirect
PyPIsnowballstemmer3.0.1indirect
PyPIsphinx—indirect
PyPIsphinx8.1.3indirect
PyPIsphinx-rtd-theme—indirect
PyPIsphinx-rtd-theme3.1.0indirect
PyPIsphinxcontrib-applehelp2.0.0indirect
PyPIsphinxcontrib-devhelp2.0.0indirect
PyPIsphinxcontrib-htmlhelp2.1.0indirect
PyPIsphinxcontrib-jquery4.1indirect
PyPIsphinxcontrib-jsmath1.0.1indirect
PyPIsphinxcontrib-qthelp2.0.0indirect
PyPIsphinxcontrib-serializinghtml2.0.0indirect
PyPItomli2.2.1indirect
PyPItyping-extensions4.14.0indirect
PyPIuart-devices0.1.1indirect
PyPIurllib32.7.0indirect
PyPIusb-devices0.4.5indirect
PyPIwinrt-runtime3.2.1indirect
PyPIwinrt-windows-devices-bluetooth3.2.1indirect
PyPIwinrt-windows-devices-bluetooth-advertisement3.2.1indirect
PyPIwinrt-windows-devices-bluetooth-genericattributeprofile3.2.1indirect
PyPIwinrt-windows-devices-enumeration3.2.1indirect
PyPIwinrt-windows-devices-radios3.2.1indirect
PyPIwinrt-windows-foundation3.2.1indirect
PyPIwinrt-windows-foundation-collections3.2.1indirect
PyPIwinrt-windows-storage-streams3.2.1indirect
Dependency advisories 0

Installing pypi:bleak-retry-connector@4.7.1 pulls in 6 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

No known advisories affect the assessed dependencies.

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.