Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-18 22:14 UTC

elliottech / lighter-python

Public Python SDK for Lighter

PythonApache-2.0★ 336 stars⑂ 162 forkssince Feb 2025View on GitHub ↗

elliottech/lighter-python holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Vitality (91/100) and lowest on Security (44/100). It was last updated 3 days ago. 3 contributors account for most of its recent work.

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

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

Ownership

136 followers17 public repossince Sep 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIlighter-sdk1.1.4-203 days agoopenapiopenapi-generator

Metrics by category

Vitality

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

91Excellent · 21% of overall
How it's scored
36/36Push recencylast push 3 days ago
21.5/36Commit cadence31/52 weeks with commits
17.4/18Commit volume86 commits in the last year
10/10OpenSSF Scorecard: Maintained12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year86
human_commit_share0.98
days_since_last_push3
active_weeks_last_year31

Release discipline

100Exceptional
How it's scored
27/27Ships releases20 releases published
36/36Release recencylatest release 3 days ago
27/27Release cadencea release every ~21.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count20
latest_release_tagv1.1.4
releases_from_tagsno
days_since_latest_release3
mean_days_between_releases21.1
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?

56Moderate · 17% of overall
How it's scored
41/60Stars336 stars
18.4/25Forks162 forks
1.7/15Watchers3 watchers
Inputs used
forks162
stars336
watchers3
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)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

67Good · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
15.6/22.5Commit distributiontop contributor authored 31% of commits
13.5/13.5Contributor breadth19 contributors
3/10OpenSSF Scorecard: Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor3
contributors_sampled19
top_contributor_share0.308
How it's scored
12.8/42Issue resolution30% of issues closed
22.1/30PR acceptance79/107 decided PRs merged
0/13Newcomer PR acceptance0/1 first-time contributors' PRs merged in 30d
7.5/15OpenSSF Scorecard: Code-ReviewFound 13/25 approved changesets -- score normalized to 5
Inputs used
merged_prs79
open_issues41
closed_issues18
prs_merged_7d1
prs_decided_7d3
prs_merged_30d5
prs_decided_30d8
issue_closed_ratio0.305
closed_unmerged_prs28
first_time_authors_30d1
first_time_prs_merged_30d0
first_time_prs_decided_30d1
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
15.4/25Owner reach136 followers of elliottech
21.1/25Track record17 public repos, account ~10 yr old
Inputs used
followers136
owner_typeOrganization
is_verifiedno
owner_loginelliottech
public_repos17
account_age_days3,666

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on pypi
35/35Publish recencylatest publish 3 days ago
20/20Version history20 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packageslighter-sdk
ecosystemspypi
any_deprecatedno
min_days_since_publish3

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter configpyproject.toml ([tool.pylint])
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests21 out of 21 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

44Weak · 16% of overall
How it's scored
3.8/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests21 out of 21 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3.8/7.5Code-ReviewFound 13/25 approved changesets -- score normalized to 5
0.8/2.5Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained12 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
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
3/7.5Vulnerabilities6 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.6
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories1 affected: urllib3 2.0.7 (high 7.5)
25/25Indirect dependencies free of known advisoriesno indirect dependency carries a known advisory
33.7/40No advisories left outstanding1 advisory-carrying package(s) unaddressed past 90 days; oldest published 823 days ago
Inputs used
sourceosv
advisories12
affected_packages1
assessed_packages40
unassessed_packages0
affected_by_severityhigh 1
direct_affected_packages1
Matched the pypi:lighter-sdk@1.1.4 runtime dependency closure — what installing the published package pulls in — 40 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.

59Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
35.9/40Legible commit history66 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.673
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configpyproject.toml ([tool.pylint])
11/11Static type checkinglighter/py.typed
0/10Reproducible environment
8/10Demonstrated agent practice4 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configslighter/py.typed
agent_commit_share0.04
toolchain_manifests
dependency_bot_commit_share0
How it's scored
27/45Type-checkable codePython with type-check config (lighter/py.typed)
53.6/55Manageable file sizes6/241 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes322,174
source_files_sampled241
oversized_source_files6
How it's scored
40/40API schema (OpenAPI/GraphQL/proto)openapi.json
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_filesopenapi.json
interfaces_expected_of
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

336GitHub stars
19contributors
86commits, last 12 months
3days since last push
20releases
3bus factor
41open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • pypi download statistics for 'lighter-sdk' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced

More detail

Star and fork history 0 ★ / 162 ⇿
0Stars
162Forks
19Releases

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.

0408012016015862025-022025-122026-09
Major 0Minor 1Patch 17

Each point covers 2 days.

OpenSSF Scorecard 3.6 / 10
3.6aggregate

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-18 22:13 UTC

5Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests21 out of 21 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 13/25 approved changesets -- score normalized to 5
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained12 commit(s) and 0 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
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
4Vulnerabilities6 existing vulnerabilities detected
Direct dependencies 9
RegistryPackageVersion constraintManifest
PyPIurllib3>= 1.25.3pyproject.toml
PyPIpython-dateutil>=2.8.2pyproject.toml
PyPIaiohttp>= 3.8.4pyproject.toml
PyPIaiohttp-retry>= 2.8.3pyproject.toml
PyPIpydantic>=2pyproject.toml
PyPItyping-extensions>=4.7.1pyproject.toml
PyPIwebsockets>= 12.0.0pyproject.toml
PyPIeth-account>=0.13.4pyproject.toml
PyPIrequests>=2.31.0pyproject.toml
All dependencies 16

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

RegistryPackageVersionRelation
PyPIaiohttpdirect
PyPIaiohttp-retrydirect
PyPIeth-accountdirect
PyPIpydanticdirect
PyPIpython-dateutildirect
PyPIrequestsdirect
PyPItyping-extensionsdirect
PyPIurllib3direct
PyPIwebsocketsdirect
PyPIflake8indirect
PyPImypyindirect
PyPImypy1.4.1indirect
PyPIpytestindirect
PyPIsetuptoolsindirect
PyPItoxindirect
PyPItypes-python-dateutilindirect
Dependency advisories 1

Installing pypi:lighter-sdk@1.1.4 pulls in 40 packages, direct and transitive: 1 carry known advisories, of which 1 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
urllib32.0.7directhigh122.7.0

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.