Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-20 15:08 UTC

mabel-dev / opteryx-core

⚙️ Opteryx Query Engine + Rugo File Driver

Python · C++ · CythonApache-2.0★ 5 stars⑂ 0 forkssince Dec 2025View on GitHub ↗
KindLibraryCommand-line toolNetwork servicehow this is determined

mabel-dev/opteryx-core holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Vitality (98/100) and lowest on Community & Adoption (47/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

OpteryxOrganization
4 followers32 public repossince May 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iocomputepoints to another repo — not scored0.2.3210331866 days agostatisticscomputedatascience
PyPIopteryx_corepoints to another repo — not scored0.9.17215,35672 days ago—
PyPIrugo0.5.45,816533 days ago—
PyPIlibskene0.3.61,727173 days ago—

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 recency — last push 0 days ago
31.8/36Commit cadence — 46/52 weeks with commits
18/18Commit volume — 1,372 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,372
human_commit_share1
days_since_last_push0
active_weeks_last_year46

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 2 days ago
27/27Release cadence — a release every ~0.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagopteryx-0.9.172
releases_from_tagsno
days_since_latest_release2
mean_days_between_releases0.9
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?

47Weak · 17% of overall
How it's scored
9.8/60Stars — 5 stars
0/25Forks — 0 forks
0/15Watchers — 0 watchers
Inputs used
forks0
stars5
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateyes
How it's scored
51.7/80Monthly downloads — 7,543 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesrugo, libskene
dependents—
ecosystemspypi
total_downloads—
monthly_downloads7,543
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?

59Moderate · 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
2.7/13.5Contributor breadth — 2 contributors
6/10OpenSSF Scorecard: Contributors — project has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.998
How it's scored
42/42Issue resolution — 100% of issues closed
24.8/30PR acceptance — 81/98 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_prs81
open_issues0
closed_issues54
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs17
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
30/30Ownership backing — organization-owned
0/20Verified domain
5/25Owner reach — 4 followers of mabel-dev
21.9/25Track record — 32 public repos, account ~5 yr old
Inputs used
followers4
owner_typeOrganization
is_verifiedno
owner_loginmabel-dev
public_repos32
account_age_days1,984

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 2 package(s) on pypi
35/35Publish recency — latest publish 3 days ago
20/20Version history — 53 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesrugo, libskene
ecosystemspypi
any_deprecatedno
min_days_since_publish3

Engineering Quality

Are baseline engineering and documentation practices in place?

91Excellent · 19% of overall
How it's scored
24/24CI workflows — 14 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff], [tool.pylint], [tool.black], [tool.isort])
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://opteryx.app
10/10Repository description
10/10Topics — 3 topics
0/10Wiki
Inputs used
topicscython, data, sql
has_wikino
homepagehttps://opteryx.app
docs_sitehttps://opteryx.app
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

59Moderate · 16% of overall
How it's scored
6/7.5Binary-Artifacts — binaries present in source code
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — no data
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
5/5Fuzzing — project is fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 3 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
5/5SAST — SAST tool detected: CodeQL
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0/7.5Vulnerabilities — 57 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.8
Excluded from scoring (no data or not applicable): CI-Tests, Signed-Releases. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories — 1 affected: pyo3 0.28.2 (high 7.5)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
33.7/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 131 days ago
Inputs used
sourceosv
advisories4
affected_packages1
assessed_packages21
unassessed_packages31
affected_by_severityhigh 1
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 21 resolved dependencies against OSV. 31 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

69Good · 4% of overall
How it's scored
45/45Agent instructions — .github/copilot-instructions.md
0/15Machine-readable docs (llms.txt)
17.1/40Legible commit history — 32 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.32
agent_instruction_files.github/copilot-instructions.md
agent_instruction_max_bytes16,650
How it's scored
18/18One-command bootstrap — Makefile, skene/Makefile, tests/fuzzing/native/Makefile, third_party/curl/Makefile, third_party/re2/Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff], [tool.pylint], [tool.black], [tool.isort])
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 5 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesCargo.lock
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile, skene/Makefile, tests/fuzzing/native/Makefile, third_party/curl/Makefile, third_party/re2/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.05
toolchain_manifestsCargo.toml
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
53.7/55Manageable file sizes — 44/1,794 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes550,957
source_files_sampled1,794
oversized_source_files44
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — third_party/curl/plan9/mkfile.proto
0/20MCP server
40/40Runnable examples — examples, notebooks
Inputs used
example_dirsexamples, notebooks
has_mcp_signalno
api_schema_filesthird_party/curl/plan9/mkfile.proto
interfaces_expected_ofnetwork-service

Key facts

5GitHub stars
2contributors
1,372commits, last 12 months
0days since last push
100releases
1bus factor
0open 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 'opteryx.third_party.mbleven' from its registry
  • crates package 'compute' points at a different repository (https://github.com/al-jshen/compute); excluded from ecosystem scoring
  • pypi package 'opteryx_core' points at a different repository (https://github.com/mabel-dev/opteryx.git); excluded from ecosystem scoring

More detail

OpenSSF Scorecard 5.8 / 10
5.8aggregate

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-20 15:07 UTC

8Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
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
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 3 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
10SASTSAST tool detected: CodeQL
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
0Vulnerabilities57 existing vulnerabilities detected
Direct dependencies 4
RegistryPackageVersion constraintManifest
crates.iopythonize0.28Cargo.toml
crates.ioserde1.0.171Cargo.toml
crates.iopyo30.28Cargo.toml
crates.iosqlparser0.63.0Cargo.toml
All dependencies 52

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

RegistryPackageVersionRelation
crates.iopyo30.28.2direct
crates.iopythonize0.28.0direct
crates.ioserde1.0.228direct
crates.iosqlparser0.63.0direct
crates.ioheck0.5.0indirect
crates.iolibc0.2.180indirect
crates.iolog0.4.29indirect
crates.ioonce_cell1.21.3indirect
crates.ioportable-atomic1.13.0indirect
crates.ioproc-macro21.0.105indirect
crates.iopyo3-build-config0.28.2indirect
crates.iopyo3-ffi0.28.2indirect
crates.iopyo3-macros0.28.2indirect
crates.iopyo3-macros-backend0.28.2indirect
crates.ioquote1.0.43indirect
crates.ioserde_core1.0.228indirect
crates.ioserde_derive1.0.228indirect
crates.iosyn2.0.114indirect
crates.iotarget-lexicon0.13.4indirect
crates.iounicode-ident1.0.22indirect
PyPIavro—indirect
PyPIblack—indirect
PyPIcoverage—indirect
PyPIcramjam—indirect
PyPIcython—indirect
PyPIduckdb—indirect
PyPIfastapi—indirect
PyPIfastavro—indirect
PyPIgoogle-cloud-storage—indirect
PyPIhypothesis—indirect
PyPIisort—indirect
PyPIjellyfish—indirect
PyPIminio—indirect
PyPImypy—indirect
PyPIopenpyxl—indirect
PyPIopteryx-catalog—indirect
PyPIorjson—indirect
PyPIprotobuf—indirect
PyPIpyarrow—indirect
PyPIpycln—indirect
PyPIpydantic2.13.5indirect
PyPIpyiceberg—indirect
PyPIpytest—indirect
PyPIpytest-xdist—indirect
PyPIpython-snappy—indirect
PyPIrich—indirect
PyPIsetuptools—indirect
PyPIsetuptools-rust—indirect
PyPItypes-orjson—indirect
PyPItypes-pyyaml—indirect
PyPIuvicorn—indirect
PyPIvalkey—indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 21 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 1 are direct. 31 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
pyo30.28.2directhigh40.29.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 statistics — crates.io, PyPI.