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

Mause / duckdb_engine

SQLAlchemy driver for DuckDB

PythonMIT★ 497 stars⑂ 70 forkssince Sep 2020View on GitHub ↗
KindPluginLibraryhow this is determined

Mause/duckdb_engine holds a health index of 66 out of 100, placing it in the Good band. It scores highest on Engineering Quality (79/100) and lowest on Vitality (59/100). It was last updated 2 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Elliana MayPersonal account
388 followers294 public repossince Feb 2012@duckdblabs

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
PyPIduckdb_engine0.17.01,843,99872532 days ago

Metrics by category

Vitality

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

59Moderate · 21% of overall
How it's scored
36/36Push recency — last push 2 days ago
1.4/36Commit cadence — 2/52 weeks with commits
15.3/18Commit volume — 50 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year50
human_commit_share0.47
days_since_last_push2
active_weeks_last_year2
How it's scored
27/27Ships releases — 68 releases published
7.2/36Release recency — latest release 532 days ago
27/27Release cadence — a release every ~15.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count68
latest_release_tagv0.17.0
releases_from_tagsno
days_since_latest_release532
mean_days_between_releases15.8
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?

73Good · 17% of overall
How it's scored
43.7/60Stars — 497 stars
15.3/25Forks — 70 forks
4.3/15Watchers — 7 watchers
Inputs used
forks70
stars497
watchers7
growth_stateorganic
growth_factor_pct100
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesbadge.fury.io, codecov.io, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads — 1,843,998 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesduckdb_engine
dependents—
ecosystemspypi
total_downloads—
monthly_downloads1,843,998
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
1.1/22.5Commit distribution — top contributor authored 95% of commits
13.5/13.5Contributor breadth — 24 contributors
10/10OpenSSF Scorecard: Contributors — project has 8 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled24
top_contributor_share0.952
How it's scored
25.5/42Issue resolution — 61% of issues closed
19.6/30PR acceptance — 790/1,211 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs790
open_issues56
closed_issues87
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.608
closed_unmerged_prs421
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
18.6/25Owner reach — 388 followers of Mause
25/25Track record — 294 public repos, account ~14 yr old
Inputs used
followers388
owner_typeUser
is_verified—
owner_loginMause
public_repos294
account_age_days5,335
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
14/35Publish recency — latest publish 532 days ago
20/20Version history — 72 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesduckdb_engine
ecosystemspypi
any_deprecatedno
min_days_since_publish532

Engineering Quality

Are baseline engineering and documentation practices in place?

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

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 5 topics
10/10Wiki
Inputs used
topicsduckdb, python, sql, sqlalchemy, duckdb-engine
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
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
0/7.5Branch-Protection — no data
2.2/2.5CI-Tests — 12 out of 13 merged PRs checked by a CI test -- score normalized to 9
0.5/2.5CII-Best-Practices — badge detected: InProgress
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 8 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
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
5/5SAST — SAST tool is run on all commits
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 22 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.3
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

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_packages5
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:duckdb_engine@0.17.0 runtime dependency closure — what installing the published package pulls in — 5 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.

76Good · 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://duckdb.org/llms.txt)
40/40Legible commit history — 38 of 47 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://duckdb.org/llms.txt
legible_history_share0.809
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — noxfile.py
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
11/11Static type checking — duckdb_engine/py.typed
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 25 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_filesnoxfile.py
has_devcontainerno
has_linter_configyes
typecheck_configsduckdb_engine/py.typed
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.25
How it's scored
27/45Type-checkable code — Python with type-check config (duckdb_engine/py.typed)
55/55Manageable file sizes — 0/14 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes24,079
source_files_sampled14
oversized_source_files0
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

497GitHub stars
24contributors
50commits, last 12 months
2days since last push
68releases
1bus factor
56open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-05-20: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 497 stars today.

More detail

Star and fork history 493 ★ / 70 ⇿
493Stars
70Forks
68Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

Star history is shown as collected on 2026-05-20. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

01002003004005004936772020-102023-092026-09
Major 0Minor 17Patch 47

Each point covers 6 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-09-12 10:28 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
9CI-Tests12 out of 13 merged PRs checked by a CI test -- score normalized to 9
2CII-Best-Practicesbadge detected: InProgress
10Code-Reviewall changesets reviewed
10Contributorsproject has 8 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities22 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
PyPIduckdb>=0.5.0pyproject.toml
PyPIsqlalchemy>=1.3.22pyproject.toml
PyPIpackaging>=21pyproject.toml
All dependencies 64

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

RegistryPackageVersionRelation
PyPIduckdb1.2.1direct
PyPIpackaging25.0direct
PyPIsqlalchemy1.4.54direct
PyPIattrs23.2.0indirect
PyPIbackoff1.11.1indirect
PyPIcertifi2024.7.4indirect
PyPIcfgv3.3.0indirect
PyPIcharset-normalizer2.0.12indirect
PyPIclick8.1.3indirect
PyPIcolorama0.4.4indirect
PyPIcoverage6.2indirect
PyPIdistlib0.3.9indirect
PyPIexceptiongroup1.0.4indirect
PyPIfancycompleter0.11.1indirect
PyPIfilelock3.16.1indirect
PyPIfsspec2025.9.0indirect
PyPIgreenlet1.1.0indirect
PyPIhypothesis6.141.1indirect
PyPIhypothesis6.142.2indirect
PyPIidentify2.2.10indirect
PyPIidna3.7indirect
PyPIiniconfig1.1.1indirect
PyPIipython-genutils0.2.0indirect
PyPIjinja23.1.6indirect
PyPIjupysql0.11.1indirect
PyPIjupysql-plugin0.4.2indirect
PyPImarkupsafe2.1.2indirect
PyPImonotonic1.6indirect
PyPImypy1.18.2indirect
PyPImypy-extensions1.0.0indirect
PyPInodeenv1.6.0indirect
PyPInumpy1.24.4indirect
PyPIpandas1.5.3indirect
PyPIpathspec0.12.1indirect
PyPIpdbpp0.11.7indirect
PyPIplatformdirs4.3.6indirect
PyPIploomber-core0.2.9indirect
PyPIpluggy1.5.0indirect
PyPIposthog2.3.1indirect
PyPIpre-commit4.3.0indirect
PyPIprettytable3.16.0indirect
PyPIpyarrow21.0.0indirect
PyPIpygments2.15.0indirect
PyPIpyreadline33.5.4indirect
PyPIpyrepl0.11.4indirect
PyPIpytest8.4.2indirect
PyPIpytest-cov5.0.0indirect
PyPIpytest-remotedata0.4.1indirect
PyPIpytest-snapshot0.9.0indirect
PyPIpython-dateutil2.8.1indirect
PyPIpytz2021.1indirect
PyPIpyyaml6.0.1indirect
PyPIrequests2.32.2indirect
PyPIsix1.16.0indirect
PyPIsortedcontainers2.4.0indirect
PyPIsqlalchemy2-stubs0.0.2a25indirect
PyPIsqlglot11.5.3indirect
PyPIsqlparse0.5.0indirect
PyPItoml0.10.2indirect
PyPItomli1.2.3indirect
PyPItyping-extensions4.6.3indirect
PyPIurllib31.26.19indirect
PyPIvirtualenv20.26.6indirect
PyPIwcwidth0.2.14indirect
Dependency advisories 0

Installing pypi:duckdb_engine@0.17.0 pulls in 5 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.