Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-09 09:04 UTC

lmmx / polars-genson

A Polars plugin for JSON schema inference from string columns using genson-rs.

Rust · PythonMIT★ 15 stars⑂ 1 forksince Aug 2025View on GitHub ↗
KindLibraryCommand-line toolNetwork servicehow this is determined

lmmx/polars-genson holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Engineering Quality (96/100) and lowest on Security (39/100). It was last updated today. A single contributor accounts for most of its recent work.

75
overall / 100
Good

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.

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

Ownership

Louis MaddoxPersonal account
216 followers363 public repossince Dec 2012

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
crates.iogenson-cli1.0.0113590 days agoclicommand-lineinferencejsonschemacommand-line-utilitiesdata-structuresparsing
crates.iogenson-core1.0.0149600 days agocoregensoninferencejsonschemadata-structuresencodingparsing
PyPIpolars-genson1.0.17,998660 days ago—
crates.iopolars-jsonschema-bridge1.0.0106210 days agoconversiondataframejsonpolarsschemadata-structuresencodingparsing

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 0 days ago
7.6/36Commit cadence — 11/52 weeks with commits
18/18Commit volume — 106 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year106
human_commit_share0.88
days_since_last_push0
active_weeks_last_year11
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~0.7 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count100
latest_release_tagpolars-jsonschema-bridge-v1.0.0
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases0.7

Community & Adoption

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

48Weak · 17% of overall
How it's scored
18.6/60Stars — 15 stars
0/25Forks — 1 forks
0/15Watchers — 1 watchers
Inputs used
forks1
stars15
watchers1
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_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
52.3/80Monthly downloads — 8,366 downloads/month across crates, pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesgenson-cli, genson-core, polars-genson, polars-jsonschema-bridge
dependents—
ecosystemscrates, pypi
total_downloads31,660
monthly_downloads8,366
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?

57Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
1.4/13.5Contributor breadth — 1 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
26.9/42Issue resolution — 64% of issues closed
29/30PR acceptance — 144/149 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs144
open_issues23
closed_issues41
prs_merged_7d7
prs_decided_7d8
prs_merged_30d32
prs_decided_30d33
issue_closed_ratio0.641
closed_unmerged_prs5
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.8/25Owner reach — 216 followers of lmmx
25/25Track record — 363 public repos, account ~13 yr old
Inputs used
followers216
owner_typeUser
is_verified—
owner_loginlmmx
public_repos363
account_age_days5,054
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 4 package(s) on crates, pypi
35/35Publish recency — latest publish 0 days ago
20/20Version history — 66 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesgenson-cli, genson-core, polars-genson, polars-jsonschema-bridge
ecosystemscrates, pypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

96Exceptional · 19% of overall
How it's scored
24/24CI workflows — 3 workflow(s)
24/24Tests present
16/16Linter config — polars-genson-py/pyproject.toml ([tool.ruff])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 10 out of 10 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

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://polars-genson.vercel.app
10/10Repository description
10/10Topics — 5 topics
10/10Wiki
Inputs used
topicsgenson, json-schema, polars-dataframe, polars-extensions, schema-inference
has_wikiyes
homepagehttps://polars-genson.vercel.app
docs_sitehttps://polars-genson.vercel.app
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

39Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
2.5/2.5CI-Tests — 10 out of 10 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/30 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 1 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
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
0/7.5Vulnerabilities — 127 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate3.9
Excluded from scoring (no data or not applicable): Packaging. Remaining weights renormalized.

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.

69Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://polars-genson.vercel.app/llms.txt)
40/40Legible commit history — 88 of 88 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://polars-genson.vercel.app/llms.txt
legible_history_share1
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Justfile
22/22Automated tests
11/11Lint / format config — polars-genson-py/pyproject.toml ([tool.ruff])
11/11Static type checking — polars-genson-py/python/polars_genson/py.typed
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 4 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
lockfilesCargo.lock, uv.lock
has_dockerfileno
typed_languageyes
bootstrap_filesJustfile
has_devcontainerno
has_linter_configyes
typecheck_configspolars-genson-py/python/polars_genson/py.typed
agent_commit_share0
toolchain_manifestsCargo.toml, genson-cli/Cargo.toml, genson-core/Cargo.toml, polars-genson-py/Cargo.toml, polars-jsonschema-bridge/Cargo.toml
dependency_bot_commit_share0.04
How it's scored
45/45Type-checkable code — Rust (statically typed)
54.1/55Manageable file sizes — 2/116 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes65,666
source_files_sampled116
oversized_source_files2
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files—
interfaces_expected_ofnetwork-service

Key facts

15GitHub stars
1contributors
106commits, last 12 months
0days since last push
100releases
1bus factor
23open issues
crates.io, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch pypi package 'polars-genson-bench' from its registry
  • Could not fetch crates package 'polars-genson-py' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • deps.dev does not index pypi:polars-genson@1.0.1; advisories assessed against the repository dependency graph instead

More detail

OpenSSF Scorecard 3.9 / 10
3.9aggregate

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-09 09:03 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests10 out of 10 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/30 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 1 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
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities127 existing vulnerabilities detected
Direct dependencies 39
RegistryPackageVersion constraintManifest
PyPIpolars-genson>=0bench/pyproject.toml
PyPIpytest-benchmark>=5.1.0bench/pyproject.toml
crates.ioanstream—genson-cli/Cargo.toml
crates.iogenson-core—genson-cli/Cargo.toml
crates.ioserde_json—genson-cli/Cargo.toml
crates.ioanstream—genson-core/Cargo.toml
crates.ioserde—genson-core/Cargo.toml
crates.ioserde_json—genson-core/Cargo.toml
crates.ioxxhash-rust—genson-core/Cargo.toml
crates.ioarrow60.0.0genson-core/Cargo.toml
crates.ioavrotize0.1.1genson-core/Cargo.toml
crates.iocrustrace0.1.9genson-core/Cargo.toml
crates.iocrustrace-mermaid0.1.6genson-core/Cargo.toml
crates.ioparquet60.0.0genson-core/Cargo.toml
crates.iotracing0.1.41genson-core/Cargo.toml
crates.iotracing-subscriber0.3.20genson-core/Cargo.toml
crates.iomimalloc—genson-core/Cargo.toml
crates.ioordermap—genson-core/Cargo.toml
crates.iorayon—genson-core/Cargo.toml
crates.ioregex—genson-core/Cargo.toml
crates.iorustc-hash—genson-core/Cargo.toml
crates.iosimd-json—genson-core/Cargo.toml
crates.iosonic-rs0.5.6genson-core/Cargo.toml
crates.ioanstream—polars-genson-py/Cargo.toml
crates.iogenson-core—polars-genson-py/Cargo.toml
crates.ioopenssl0.10polars-genson-py/Cargo.toml
crates.iopolars—polars-genson-py/Cargo.toml
crates.iopolars-arrow—polars-genson-py/Cargo.toml
crates.iopolars-expr—polars-genson-py/Cargo.toml
crates.iopolars-jsonschema-bridge—polars-genson-py/Cargo.toml
crates.iopyo3—polars-genson-py/Cargo.toml
crates.iopyo3-polars—polars-genson-py/Cargo.toml
crates.iorayon—polars-genson-py/Cargo.toml
crates.ioserde—polars-genson-py/Cargo.toml
crates.ioserde_json—polars-genson-py/Cargo.toml
PyPIorjson>=3.11.2polars-genson-py/pyproject.toml
crates.ioanstream—polars-jsonschema-bridge/Cargo.toml
crates.iopolars—polars-jsonschema-bridge/Cargo.toml
crates.ioserde_json—polars-jsonschema-bridge/Cargo.toml
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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 — crates.io, PyPI.