Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-16 06:48 UTC

openlayer-ai / openlayer-python

The official Python library for Openlayer, the Continuous Model Improvement Platform for AI. 📈

PythonApache-2.0★ 18 stars⑂ 2 forkssince Feb 2021View on GitHub ↗

openlayer-ai/openlayer-python holds a health index of 90 out of 100, placing it in the Excellent band. It scores highest on Vitality (97/100) and lowest on Community & Adoption (56/100). It was last updated 6 days ago. 2 contributors account for most of its recent work.

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

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

Ownership

OpenlayerOrganization
26 followers8 public repossince Feb 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIopenlayer0.32.0129,4032226 days ago

Metrics by category

Vitality

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

97Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 6 days ago
31.2/36Commit cadence — 45/52 weeks with commits
18/18Commit volume — 227 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year227
human_commit_share0.41
days_since_last_push6
active_weeks_last_year45

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 6 days ago
27/27Release cadence — a release every ~12.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv0.32.0
releases_from_tagsno
days_since_latest_release6
mean_days_between_releases12.2
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
20/60Stars — 18 stars
0/25Forks — 2 forks
0/15Watchers — 2 watchers
Inputs used
forks2
stars18
watchers2
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_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
68.2/80Monthly downloads — 129,403 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesopenlayer
dependents—
ecosystemspypi
total_downloads—
monthly_downloads129,403
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?

72Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
12.1/22.5Commit distribution — top contributor authored 46% of commits
13.5/13.5Contributor breadth — 12 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled12
top_contributor_share0.462
How it's scored
21/42Issue resolution — 50% of issues closed
28.6/30PR acceptance — 637/669 decided PRs merged
13/13Newcomer PR acceptance — 2/2 first-time contributors' PRs merged in 30d
15/15OpenSSF Scorecard: Code-Review — all changesets reviewed
Inputs used
merged_prs637
open_issues1
closed_issues1
prs_merged_7d2
prs_decided_7d4
prs_merged_30d4
prs_decided_30d6
issue_closed_ratio0.5
closed_unmerged_prs32
first_time_authors_30d1
first_time_prs_merged_30d2
first_time_prs_decided_30d2
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
10.3/25Owner reach — 26 followers of openlayer-ai
18.2/25Track record — 8 public repos, account ~5 yr old
Inputs used
followers26
owner_typeOrganization
is_verifiedno
owner_loginopenlayer-ai
public_repos8
account_age_days2,046

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 6 days ago
20/20Version history — 222 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesopenlayer
ecosystemspypi
any_deprecatedno
min_days_since_publish6

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows — 6 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 13 out of 13 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
0/25Documentation directory
15/15Documentation / homepage site — https://www.openlayer.com
10/10Repository description
10/10Topics — 13 topics
10/10Wiki
Inputs used
topicsai, data-centric, machine-learning, machine-learning-operations, ml, ml-infrastructure, mlops, model-deployment, model-explainability, synthetic-dataset-generation, tensorflow, unbox, openlayer
has_wikiyes
homepagehttps://www.openlayer.com
docs_sitehttps://www.openlayer.com
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

70Good · 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.5/2.5CI-Tests — 13 out of 13 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
7.5/7.5Code-Review — all changesets reviewed
2.5/2.5Contributors — project has 4 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
1/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.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_packages25
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:openlayer@0.32.0 runtime dependency closure — what installing the published package pulls in — 25 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.

77Good · 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://www.openlayer.com/llms.txt)
40/40Legible commit history — 38 of 41 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://www.openlayer.com/llms.txt
legible_history_share0.927
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 — src/openlayer/py.typed
10/10Reproducible environment — devcontainer, Dockerfile
10/10Demonstrated agent practice — 14 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
2/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_filesnoxfile.py
has_devcontaineryes
has_linter_configyes
typecheck_configssrc/openlayer/py.typed
agent_commit_share0.14
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (src/openlayer/py.typed)
53.3/55Manageable file sizes — 7/222 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes114,766
source_files_sampled222
oversized_source_files7
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, notebooks
Inputs used
example_dirsexamples, notebooks
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

18GitHub stars
12contributors
227commits, last 12 months
6days since last push
100releases
2bus factor
1open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 2 ⇿
0Stars
2Forks
28Releases

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.

111222212024-072025-032025-11
Major 0Minor 2Patch 1

Each point covers 2 days.

OpenSSF Scorecard 6.3 / 10
6.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-16 06:47 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
10CI-Tests13 out of 13 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
10Code-Reviewall changesets reviewed
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 13
RegistryPackageVersion constraintManifest
PyPIhttpx>=0.23.0, <1pyproject.toml
PyPIpydantic>=1.9.0, <3pyproject.toml
PyPItyping-extensions>=4.14, <5pyproject.toml
PyPIanyio>=3.5.0, <5pyproject.toml
PyPIdistro>=1.7.0, <2pyproject.toml
PyPIsniffio—pyproject.toml
PyPIpandas—pyproject.toml
PyPIpyarrow>=15.0.2,<=17.0.0pyproject.toml
PyPIpyarrow>=18.0.0pyproject.toml
PyPIpyyaml>=6.0pyproject.toml
PyPIrequests_toolbelt>=1.0.0pyproject.toml
PyPItqdm—pyproject.toml
PyPIwrapt>=1.14.0pyproject.toml
All dependencies 11

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

RegistryPackageVersionRelation
PyPIanyio—direct
PyPIdistro—direct
PyPIhttpx—direct
PyPIpyarrow—direct
PyPIpydantic—direct
PyPIpyyaml—direct
PyPIrequests-toolbelt—direct
PyPItyping-extensions—direct
PyPIwrapt—direct
PyPIhatchling1.26.3indirect
PyPIhttpx-aiohttp—indirect
Dependency advisories 0

Installing pypi:openlayer@0.32.0 pulls in 25 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.