Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-25 08:26 UTC

gr4vy / gr4vy-python

Gr4vy SDK for Python

PythonNo license detected★ 1 star⑂ 4 forkssince Oct 2021View on GitHub ↗

gr4vy/gr4vy-python holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Vitality (96/100) and lowest on Community & Adoption (34/100). It was last updated today. A single contributor accounts 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

Gr4vyOrganization · verified domain
29 followers45 public repossince Feb 2016

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIgr4vy2.4.185,6512730 days ago

Metrics by category

Vitality

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

96Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
29.8/36Commit cadence — 43/52 weeks with commits
18/18Commit volume — 191 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_year191
human_commit_share0.1
days_since_last_push0
active_weeks_last_year43

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~1.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv2.4.18
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases1.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?

34At Risk · 17% of overall
How it's scored
0/60Stars — 1 stars
4/25Forks — 4 forks
1.7/15Watchers — 3 watchers
Inputs used
forks4
stars1
watchers3
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5License — no license file detected
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
50/80Monthly downloads — 5,651 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesgr4vy
dependents—
ecosystemspypi
total_downloads—
monthly_downloads5,651
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?

68Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
7.7/22.5Commit distribution — top contributor authored 66% of commits
9.5/13.5Contributor breadth — 7 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled7
top_contributor_share0.658
How it's scored
0/42Issue resolution — no issues or no data
27.8/30PR acceptance — 301/325 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/6 approved changesets -- score normalized to 0
Inputs used
merged_prs301
open_issues0
closed_issues0
prs_merged_7d1
prs_decided_7d1
prs_merged_30d3
prs_decided_30d3
issue_closed_ratio—
closed_unmerged_prs24
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
20/20Verified domain
10.6/25Owner reach — 29 followers of gr4vy
24.1/25Track record — 45 public repos, account ~10 yr old
Inputs used
followers29
owner_typeOrganization
is_verifiedyes
owner_logingr4vy
public_repos45
account_age_days3,880

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

77Good · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 29 out of 29 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://docs.gr4vy.com
10/10Repository description
10/10Topics — 5 topics
0/10Wiki
Inputs used
topicsgr4vy, orchestration, payments, python, sdk
has_wikino
homepagehttps://docs.gr4vy.com
docs_sitehttps://docs.gr4vy.com
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

63Moderate · 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 — 29 out of 29 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/6 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 4 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
0/2.5License — license file not 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
5/5Pinned-Dependencies — all dependencies are pinned
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 — 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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5.4
Excluded from scoring (no data or not applicable): 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
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories4
affected_packages2
assessed_packages48
unassessed_packages0
affected_by_severityhigh 2
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 48 resolved dependencies against OSV. 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.

57Moderate · 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://docs.gr4vy.com/llms.txt)
0/40Legible commit history — no data
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.gr4vy.com/llms.txt
legible_history_share—
agent_instruction_files—
agent_instruction_max_bytes—
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
0/11Lint / format config
11/11Static type checking — py.typed, src/gr4vy/py.typed
0/10Reproducible environment
10/10Demonstrated agent practice — 10 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
10/10OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configspy.typed, src/gr4vy/py.typed
agent_commit_share0.1
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (py.typed, src/gr4vy/py.typed)
53.9/55Manageable file sizes — 12/607 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes194,807
source_files_sampled607
oversized_source_files12

Key facts

1GitHub stars
7contributors
191commits, last 12 months
0days since last push
100releases
1bus factor
0open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index pypi:gr4vy@2.4.18; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 4 ⇿
0Stars
4Forks
6Releases

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.

1223344422023-072024-112026-04
Major 0Minor 0Patch 6

Each point covers 3 days.

OpenSSF Scorecard 5.4 / 10
5.4aggregate

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-25 08:26 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests29 out of 29 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/6 approved changesets -- score normalized to 0
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not detected
10Maintained30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
10Pinned-Dependenciesall dependencies are pinned
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
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
PyPIPyJWT(>=2.10.1,<3.0.0)pyproject.toml
PyPIcryptography(>=50.0.1,<51.0.0)pyproject.toml
PyPIhttpcore>=1.0.9pyproject.toml
PyPIhttpx>=0.28.1pyproject.toml
PyPIjsonpath-python>=1.0.6pyproject.toml
PyPIpydantic>=2.11.2pyproject.toml
PyPIpython-jose(>=3.4.0,<4.0.0)pyproject.toml
All dependencies 48

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

RegistryPackageVersionRelation
PyPIcryptography50.0.1direct
PyPIhttpcore1.0.9direct
PyPIhttpx0.28.1direct
PyPIjsonpath-python1.1.6direct
PyPIpydantic2.13.5direct
PyPIpyjwt2.15.0direct
PyPIpython-jose3.5.0direct
PyPIannotated-types0.8.0indirect
PyPIanyio4.15.1indirect
PyPIastroid3.2.4indirect
PyPIcertifi2026.7.22indirect
PyPIcffi2.1.1indirect
PyPIcharset-normalizer3.5.1indirect
PyPIcolorama0.4.6indirect
PyPIdill0.4.1indirect
PyPIecdsa0.19.2indirect
PyPIexceptiongroup1.3.1indirect
PyPIfreezegun1.5.5indirect
PyPIh110.16.0indirect
PyPIidna3.20indirect
PyPIiniconfig2.3.0indirect
PyPIisort5.13.2indirect
PyPImccabe0.7.0indirect
PyPImypy1.15.0indirect
PyPImypy-extensions1.1.0indirect
PyPInodeenv1.10.0indirect
PyPIpackaging26.3indirect
PyPIplatformdirs4.11.13indirect
PyPIpluggy1.6.0indirect
PyPIpyasn10.6.4indirect
PyPIpycparser3.0indirect
PyPIpydantic-core2.46.5indirect
PyPIpygments2.21.0indirect
PyPIpylint3.2.3indirect
PyPIpyright1.1.398indirect
PyPIpytest9.1.1indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIrequests2.34.2indirect
PyPIrsa4.2indirect
PyPIsix1.17.0indirect
PyPItomli2.4.1indirect
PyPItomlkit0.15.1indirect
PyPItypes-pyasn10.6.0.20260724indirect
PyPItypes-pygments2.21.0.20260819indirect
PyPItypes-python-jose3.5.0.20260408indirect
PyPItyping-extensions4.16.0indirect
PyPItyping-inspection0.4.4indirect
PyPIurllib32.8.0indirect
Dependency advisories 2

This repository publishes no package the index resolves, so its own dependency graph was assessed — 48 packages, which also include development and test pins that never ship: 2 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
ecdsa0.19.2indirecthigh2—
rsa4.2indirecthigh24.7

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.