Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-18 02:06 UTC

Djelibeybi / lifx-async

A modern, type-safe, async Python library for controlling LIFX lights

PythonUPL-1.0★ 7 stars⑂ 1 forksince Nov 2025View on GitHub ↗

Djelibeybi/lifx-async holds a health index of 88 out of 100, placing it in the Excellent band. It scores highest on Vitality (94/100) and lowest on Community & Adoption (40/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Avi MillerPersonal account
184 followers47 public repossince Jul 2009@ColourWithin

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 publish
PyPIlifx-async8.0.113,4111283 days ago

Metrics by category

Vitality

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

94Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
32.5/36Commit cadence — 47/52 weeks with commits
18/18Commit volume — 752 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 29 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year752
human_commit_share0.89
days_since_last_push0
active_weeks_last_year47
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 3 days ago
27/27Release cadence — a release every ~3.4 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagv8.0.1
releases_from_tagsno
days_since_latest_release3
mean_days_between_releases3.4

Community & Adoption

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

40Weak · 17% of overall
How it's scored
12.6/60Stars — 7 stars
0/25Forks — 1 forks
0/15Watchers — 1 watchers
Inputs used
forks1
stars7
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (UPL-1.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges6
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com, shields.io
has_pull_request_templateno
How it's scored
55/80Monthly downloads — 13,411 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageslifx-async
dependents—
ecosystemspypi
total_downloads—
monthly_downloads13,411
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?

60Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.1/22.5Commit distribution — top contributor authored 100% of commits
4.1/13.5Contributor breadth — 3 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.997
How it's scored
38/42Issue resolution — 90% of issues closed
29/30PR acceptance — 263/272 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/6 approved changesets -- score normalized to 0
Inputs used
merged_prs263
open_issues7
closed_issues66
prs_merged_7d2
prs_decided_7d2
prs_merged_30d5
prs_decided_30d5
issue_closed_ratio0.904
closed_unmerged_prs9
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
16.3/25Owner reach — 184 followers of Djelibeybi
24.2/25Track record — 47 public repos, account ~17 yr old
Inputs used
followers184
owner_typeUser
is_verified—
owner_loginDjelibeybi
public_repos47
account_age_days6,340
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 3 days ago
20/20Version history — 128 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageslifx-async
ecosystemspypi
any_deprecatedno
min_days_since_publish3

Engineering Quality

Are baseline engineering and documentation practices in place?

92Excellent · 19% of overall
How it's scored
24/24CI workflows — 4 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 — 9 out of 9 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

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://djelibeybi.github.io/lifx-async/
10/10Repository description
10/10Topics — 7 topics
0/10Wiki
Inputs used
topicsasyncio, asyncio-python, lifx, lifx-bulbs, lifx-lan-protocol, lifx-lights, llms-txt
has_wikino
homepagehttps://djelibeybi.github.io/lifx-async/
docs_sitehttps://djelibeybi.github.io/lifx-async/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

78Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
3/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 9 out of 9 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/6 approved changesets -- score normalized to 0
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
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 29 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
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
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_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate7.3

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
advisories0
affected_packages0
assessed_packages67
unassessed_packages0
affected_by_severitynone
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 67 resolved dependencies against OSV. 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 — AGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://djelibeybi.github.io/lifx-async/llms.txt)
32.4/40Legible commit history — 54 of 89 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://djelibeybi.github.io/lifx-async/llms.txt
legible_history_share0.607
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes35,644
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
11/11Static type checking — src/lifx/py.typed
10/10Reproducible environment — lockfile
10/10Demonstrated agent practice — 45 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 10 of the last 100 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configssrc/lifx/py.typed
agent_commit_share0.45
toolchain_manifests—
dependency_bot_commit_share0.1
How it's scored
27/45Type-checkable code — Python with type-check config (src/lifx/py.typed)
52.5/55Manageable file sizes — 17/373 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes339,434
source_files_sampled373
oversized_source_files17
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

7GitHub stars
3contributors
752commits, last 12 months
0days since last push
100releases
1bus factor
7open 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:lifx-async@8.0.1; advisories assessed against the repository dependency graph instead

More detail

OpenSSF Scorecard 7.3 / 10
7.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-18 02:06 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests9 out of 9 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/6 approved changesets -- score normalized to 0
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 29 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
0Signed-ReleasesProject has not signed or included provenance with any releases.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 67

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

RegistryPackageVersionRelation
PyPIannotated-doc0.0.4indirect
PyPIannotated-types0.7.0indirect
PyPIbeautifulsoup44.15.0indirect
PyPIclick8.4.2indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.15.0indirect
PyPIdeepmerge2.1.0indirect
PyPIghp-import2.1.0indirect
PyPIgriffelib2.1.0indirect
PyPIhatchling1.30.1indirect
PyPIifaddr0.2.0indirect
PyPIiniconfig2.3.0indirect
PyPIjinja23.1.6indirect
PyPIlifx-async8.0.1indirect
PyPIlifx-emulator-core3.15.0indirect
PyPIllmstxt-standalone0.2.0indirect
PyPImarkdown3.10.2indirect
PyPImarkdown-it-py3.0.0indirect
PyPImarkdownify1.2.3indirect
PyPImarkupsafe3.0.3indirect
PyPImdformat0.7.22indirect
PyPImdformat-tables1.0.0indirect
PyPImdurl0.1.2indirect
PyPImergedeep1.3.4indirect
PyPImkdocs1.6.1indirect
PyPImkdocs-autorefs1.4.4indirect
PyPImkdocs-get-deps0.2.2indirect
PyPImkdocstrings1.0.4indirect
PyPImkdocstrings-python2.0.5indirect
PyPInodeenv1.10.0indirect
PyPIpackaging26.2indirect
PyPIpathspec1.1.1indirect
PyPIplatformdirs4.10.0indirect
PyPIpluggy1.6.0indirect
PyPIprek0.4.8indirect
PyPIpy-cpuinfo9.0.0indirect
PyPIpydantic2.14.2indirect
PyPIpydantic-core2.50.2indirect
PyPIpygments2.20.0indirect
PyPIpymdown-extensions11.0.1indirect
PyPIpyright1.1.411indirect
PyPIpytest9.1.1indirect
PyPIpytest-asyncio1.4.0indirect
PyPIpytest-benchmark5.2.3indirect
PyPIpytest-cov7.1.0indirect
PyPIpytest-retry1.7.0indirect
PyPIpytest-sugar1.1.1indirect
PyPIpytest-timeout2.4.0indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpyyaml6.0.3indirect
PyPIpyyaml-env-tag1.1indirect
PyPIrich15.0.0indirect
PyPIruamel-yaml0.19.1indirect
PyPIruff0.15.20indirect
PyPIshellingham1.5.4indirect
PyPIsix1.17.0indirect
PyPIsoupsieve4.1indirect
PyPItermcolor3.3.0indirect
PyPItomli2.4.1indirect
PyPItrove-classifiers2026.6.1.19indirect
PyPItyper0.26.8indirect
PyPItyping-extensions4.16.0indirect
PyPItyping-inspection0.4.4indirect
PyPIwatchdog6.0.0indirect
PyPIwcwidth0.8.2indirect
PyPIzensical0.0.47indirect
PyPIzeroconf0.151.5indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 67 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct.

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.