Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-15 23:35 UTC

Python-roborock / python-roborock

Python library & console tool for controlling Roborock vacuum

PythonApache-2.0★ 230 stars⑂ 104 forkssince Feb 2023View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

Python-roborock/python-roborock holds a health index of 92 out of 100, placing it in the Excellent band. It scores highest on Vitality (98/100) and lowest on Security (63/100). It was last updated 2 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

Python-roborockOrganization
8 followers4 public repossince Jan 2025

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIpython-roborock7.8.081,9964522 days agohomeassistantroborockvacuum

Metrics by category

Vitality

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

98Exceptional · 21% of overall
How it's scored
36/36Push recencylast push 2 days ago
31.8/36Commit cadence46/52 weeks with commits
18/18Commit volume555 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year555
human_commit_share1
days_since_last_push2
active_weeks_last_year46

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 2 days ago
27/27Release cadencea release every ~0.7 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tagv7.8.0
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases0.7
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

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

69Good · 17% of overall
How it's scored
38.3/60Stars230 stars
16.8/25Forks104 forks
4.3/15Watchers7 watchers
Inputs used
forks104
stars230
watchers7
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, shields.io
has_pull_request_templateno
How it's scored
65.5/80Monthly downloads81,996 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagespython-roborock
dependents
ecosystemspypi
total_downloads
monthly_downloads81,996
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?

68Good · 23% of overall
How it's scored
25.2/54Bus factor2 contributor(s) cover half of all commits
14.6/22.5Commit distributiontop contributor authored 35% of commits
13.5/13.5Contributor breadth59 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled59
top_contributor_share0.351
How it's scored
28.4/42Issue resolution68% of issues closed
24.6/30PR acceptance661/806 decided PRs merged
11.7/13Newcomer PR acceptance9/10 first-time contributors' PRs merged in 30d
7.5/15OpenSSF Scorecard: Code-ReviewFound 17/30 approved changesets -- score normalized to 5
Inputs used
merged_prs661
open_issues43
closed_issues90
prs_merged_7d11
prs_decided_7d12
prs_merged_30d23
prs_decided_30d25
issue_closed_ratio0.677
closed_unmerged_prs145
first_time_authors_30d6
first_time_prs_merged_30d9
first_time_prs_decided_30d10
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
6.9/25Owner reach8 followers of Python-roborock
8.5/25Track record4 public repos, account ~1 yr old
Inputs used
followers8
owner_typeOrganization
is_verifiedno
owner_loginPython-roborock
public_repos4
account_age_days618

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on pypi
35/35Publish recencylatest publish 2 days ago
20/20Version history452 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagespython-roborock
ecosystemspypi
any_deprecatedno
min_days_since_publish2

Engineering Quality

Are baseline engineering and documentation practices in place?

91Excellent · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter configpyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests16 out of 17 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://python-roborock.github.io/python-roborock/
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepagehttps://python-roborock.github.io/python-roborock/
docs_sitehttps://python-roborock.github.io/python-roborock/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

63Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
4.5/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.2/2.5CI-Tests16 out of 17 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-ReviewFound 17/30 approved changesets -- score normalized to 5
2.5/2.5Contributorsproject has 4 contributing companies or organizations
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 4 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
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities50 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate5.4
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages18
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:python-roborock@7.8.0 runtime dependency closure — what installing the published package pulls in — 18 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.

77Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md, CLAUDE.md
0/15Machine-readable docs (llms.txt)
31.5/40Legible commit history59 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.59
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes8,985
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configpyproject.toml ([tool.ruff])
11/11Static type checkingmypy.ini, roborock/py.typed
10/10Reproducible environmentlockfile
8/10Demonstrated agent practice4 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency 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_configsmypy.ini, roborock/py.typed
agent_commit_share0.04
toolchain_manifests
dependency_bot_commit_share0
How it's scored
27/45Type-checkable codePython with type-check config (mypy.ini, roborock/py.typed)
54.8/55Manageable file sizes1/230 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes63,321
source_files_sampled230
oversized_source_files1
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)roborock/map/proto/b01_scmap.proto
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_filesroborock/map/proto/b01_scmap.proto
interfaces_expected_of
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

230GitHub stars
59contributors
555commits, last 12 months
2days since last push
100releases
2bus factor
43open 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 ★ / 104 ⇿
0Stars
104Forks
94Releases

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.

02040608010012010442023-022024-122026-09
Major 3Minor 61Patch 30

Each point covers 4 days.

OpenSSF Scorecard 5.4 / 10
5.4aggregate

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-15 23:34 UTC

10Binary-Artifactsno binaries found in the repo
6Branch-Protectionbranch protection is not maximal on development and all release branches
9CI-Tests16 out of 17 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 17/30 approved changesets -- score normalized to 5
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 4 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
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities50 existing vulnerabilities detected
Direct dependencies 9
RegistryPackageVersion constraintManifest
PyPIaiohttp>=3.8.2,<4pyproject.toml
PyPIpycryptodome~=3.18pyproject.toml
PyPIpycryptodomex~=3.18pyproject.toml
PyPIpaho-mqtt>=1.6.1,<3.0.0pyproject.toml
PyPIconstruct>=2.10.57,<3pyproject.toml
PyPIprotobuf>=6.31.1,<8pyproject.toml
PyPIvacuum-map-parser-roborockpyproject.toml
PyPIpyrate-limiter>=4.0.0,<5pyproject.toml
PyPIaiomqtt>=2.5.0,<3pyproject.toml
All dependencies 61

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

RegistryPackageVersionRelation
PyPIaiohttp3.13.3direct
PyPIaiomqtt2.5.0direct
PyPIconstruct2.10.70direct
PyPIpaho-mqtt2.1.0direct
PyPIprotobuf6.33.6direct
PyPIpycryptodome3.23.0direct
PyPIpycryptodomex3.23.0direct
PyPIpyrate-limiter4.0.2direct
PyPIvacuum-map-parser-roborock0.1.5direct
PyPIaiohappyeyeballs2.6.1indirect
PyPIaioresponses0.7.8indirect
PyPIaiosignal1.4.0indirect
PyPIappdirs1.4.4indirect
PyPIattrs25.4.0indirect
PyPIcfgv3.4.0indirect
PyPIclick8.3.1indirect
PyPIclick-shell2.1indirect
PyPIcodespell2.4.1indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.12.0indirect
PyPIdistlib0.4.0indirect
PyPIfilelock3.20.0indirect
PyPIfreezegun1.5.5indirect
PyPIfrozenlist1.8.0indirect
PyPIidentify2.6.15indirect
PyPIidna3.10indirect
PyPIiniconfig2.3.0indirect
PyPIjinja23.1.6indirect
PyPIlibrt0.7.3indirect
PyPIlxml6.0.2indirect
PyPImarkdown22.5.4indirect
PyPImarkupsafe3.0.3indirect
PyPImultidict6.7.0indirect
PyPImypy1.19.1indirect
PyPImypy-extensions1.1.0indirect
PyPInodeenv1.9.1indirect
PyPIpackaging25.0indirect
PyPIpathspec0.12.1indirect
PyPIpdoc16.0.0indirect
PyPIpillow11.3.0indirect
PyPIplatformdirs4.5.0indirect
PyPIpluggy1.6.0indirect
PyPIpre-commit4.5.1indirect
PyPIpropcache0.4.1indirect
PyPIpygments2.19.2indirect
PyPIpyshark0.6indirect
PyPIpytest9.0.2indirect
PyPIpytest-asyncio1.3.0indirect
PyPIpytest-cov7.0.0indirect
PyPIpytest-timeout2.4.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpyyaml6.0.3indirect
PyPIruff0.14.11indirect
PyPIsix1.17.0indirect
PyPIsyrupy5.0.0indirect
PyPItermcolor3.1.0indirect
PyPItomli2.3.0indirect
PyPItyping-extensions4.15.0indirect
PyPIvacuum-map-parser-base0.1.5indirect
PyPIvirtualenv20.35.3indirect
PyPIyarl1.22.0indirect
Dependency advisories 0

Installing pypi:python-roborock@7.8.0 pulls in 18 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 statisticsPyPI.