Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-17 07:01 UTC

vibrantlabsai / ragas

Supercharge Your LLM Application Evaluations 🚀

Python · Jupyter NotebookApache-2.0★ 15,758 stars⑂ 1,704 forkssince May 2023View on GitHub ↗
KindCommand-line toolPluginLibraryhow this is determined

vibrantlabsai/ragas holds a health index of 86 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (95/100) and lowest on Security (53/100). It was last updated 204 days ago. 2 contributors account 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

Vibrant LabsOrganization
354 followers17 public repossince Jan 2023

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIragas0.4.31,193,75788246 days ago

Metrics by category

Vitality

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

53Moderate · 21% of overall
How it's scored
3.6/36Push recency — last push 204 days ago
14.5/36Commit cadence — 21/52 weeks with commits
18/18Commit volume — 183 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_year183
human_commit_share1
days_since_last_push204
active_weeks_last_year21
How it's scored
27/27Ships releases — 89 releases published
16.2/36Release recency — latest release 246 days ago
27/27Release cadence — a release every ~13.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count89
latest_release_tagv0.4.3
releases_from_tagsno
days_since_latest_release246
mean_days_between_releases13.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?

95Exceptional · 17% of overall
How it's scored
60/60Stars — 15,758 stars
25/25Forks — 1,704 forks
10/15Watchers — 64 watchers
Inputs used
forks1,704
stars15,758
watchers64
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
80/80Monthly downloads — 1,193,757 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesragas
dependents—
ecosystemspypi
total_downloads—
monthly_downloads1,193,757
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?

69Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
16.2/22.5Commit distribution — top contributor authored 28% of commits
13.5/13.5Contributor breadth — 100 contributors
10/10OpenSSF Scorecard: Contributors — project has 13 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled100
top_contributor_share0.279
How it's scored
30.4/42Issue resolution — 72% of issues closed
23.5/30PR acceptance — 1,122/1,433 decided PRs merged
0/13Newcomer PR acceptance — 0/20 first-time contributors' PRs merged in 30d
6/15OpenSSF Scorecard: Code-Review — Found 12/30 approved changesets -- score normalized to 4
Inputs used
merged_prs1,122
open_issues373
closed_issues974
prs_merged_7d0
prs_decided_7d13
prs_merged_30d0
prs_decided_30d20
issue_closed_ratio0.723
closed_unmerged_prs311
first_time_authors_30d8
first_time_prs_merged_30d0
first_time_prs_decided_30d20
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
18.3/25Owner reach — 354 followers of vibrantlabsai
16.5/25Track record — 17 public repos, account ~3 yr old
Inputs used
followers354
owner_typeOrganization
is_verifiedno
owner_loginvibrantlabsai
public_repos17
account_age_days1,342
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
26/35Publish recency — latest publish 246 days ago
20/20Version history — 88 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesragas
ecosystemspypi
any_deprecatedno
min_days_since_publish246

Engineering Quality

Are baseline engineering and documentation practices in place?

91Excellent · 19% of overall
How it's scored
24/24CI workflows — 8 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 — 29 out of 30 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

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://docs.ragas.io
10/10Repository description
10/10Topics — 3 topics
0/10Wiki
Inputs used
topicsllm, llmops, evaluation
has_wikino
homepagehttps://docs.ragas.io
docs_sitehttps://docs.ragas.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

53Moderate · 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 — 29 out of 30 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3/7.5Code-Review — Found 12/30 approved changesets -- score normalized to 4
2.5/2.5Contributors — project has 13 contributing companies or organizations
0/10Dangerous-Workflow — 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
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
5/5Packaging — packaging workflow detected
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
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
5.2/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_aggregate4.5
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.
How it's scored
24.5/35Direct dependencies free of known advisories — 2 affected: diskcache 5.6.3 (moderate), langchain-openai 1.1.9 (low 3.1)
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
34.7/40No advisories left outstanding — 2 advisory-carrying package(s) unaddressed past 90 days; oldest published 217 days ago
Inputs used
sourceosv
advisories4
affected_packages2
assessed_packages90
unassessed_packages0
affected_by_severitymoderate 1, low 1
direct_affected_packages2
Matched the pypi:ragas@0.4.3 runtime dependency closure — what installing the published package pulls in — 90 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.

87Excellent · 4% of overall
How it's scored
45/45Agent instructions — .cursor/rules/docs-diataxis-guidelines.mdc, .cursor/rules/docs-structure.mdc, .cursor/rules/project-structure.mdc, .cursor/rules/update-guide.mdc, .cursor/rules/use-uv-cli.mdc, CLAUDE.md, docs/concepts/metrics/available_metrics/agents.md, docs/concepts/test_data_generation/agents.md, docs/howtos/integrations/gemini.md, docs/tutorials/agent.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.ragas.io/llms.txt)
40/40Legible commit history — 100 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://docs.ragas.io/llms.txt
legible_history_share1
agent_instruction_files.cursor/rules/docs-diataxis-guidelines.mdc, .cursor/rules/docs-structure.mdc, .cursor/rules/project-structure.mdc, .cursor/rules/update-guide.mdc, .cursor/rules/use-uv-cli.mdc, CLAUDE.md, docs/concepts/metrics/available_metrics/agents.md, docs/concepts/test_data_generation/agents.md, docs/howtos/integrations/gemini.md, docs/tutorials/agent.md
agent_instruction_max_bytes24,135
How it's scored
18/18One-command bootstrap — Makefile, docs/Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
11/11Static type checking — src/ragas/py.typed
10/10Reproducible environment — Dockerfile
2/10Demonstrated agent practice — 1 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_filesMakefile, docs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configssrc/ragas/py.typed
agent_commit_share0.01
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (src/ragas/py.typed)
55/55Manageable file sizes — 0/392 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes51,892
source_files_sampled392
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, 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

15,758GitHub stars
100contributors
183commits, last 12 months
204days since last push
89releases
2bus factor
373open 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 ★ / 1,704 ⇿
0Stars
1,704Forks
32Releases

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.

5007501,0001,2501,5001,7501,704142024-112025-102026-09
Major 0Minor 2Patch 22

Each point covers 2 days.

OpenSSF Scorecard 4.5 / 10
4.5aggregate

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-17 07:00 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-Tests29 out of 30 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 12/30 approved changesets -- score normalized to 4
10Contributorsproject has 13 contributing companies or organizations
0Dangerous-Workflowdangerous workflow patterns detected
0Dependency-Update-Toolno update 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
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
7Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 19
RegistryPackageVersion constraintManifest
PyPInumpy>=1.21.0,<3.0.0pyproject.toml
PyPIdatasets>=4.0.0pyproject.toml
PyPItiktoken—pyproject.toml
PyPIpydantic>=2.0.0pyproject.toml
PyPInest-asyncio—pyproject.toml
PyPIappdirs—pyproject.toml
PyPIdiskcache>=5.6.3pyproject.toml
PyPItyper—pyproject.toml
PyPIrich—pyproject.toml
PyPIopenai>=1.0.0pyproject.toml
PyPItqdm—pyproject.toml
PyPIinstructor—pyproject.toml
PyPIpillow>=10.4.0pyproject.toml
PyPInetworkx—pyproject.toml
PyPIscikit-network—pyproject.toml
PyPIlangchain—pyproject.toml
PyPIlangchain-core—pyproject.toml
PyPIlangchain-community—pyproject.toml
PyPIlangchain_openai—pyproject.toml
All dependencies 25

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

RegistryPackageVersionRelation
PyPIappdirs—direct
PyPIdatasets—direct
PyPIdiskcache—direct
PyPIinstructor—direct
PyPIlangchain—direct
PyPIlangchain-community—direct
PyPIlangchain-core—direct
PyPIlangchain-openai—direct
PyPInest-asyncio—direct
PyPInetworkx—direct
PyPInumpy—direct
PyPIopenai—direct
PyPIpillow—direct
PyPIpydantic—direct
PyPIrich—direct
PyPIscikit-network—direct
PyPItiktoken—direct
PyPItqdm—direct
PyPItyper—direct
PyPIlangchain-text-splitters—indirect
PyPImlflow—indirect
PyPIpandas—indirect
PyPIpython-dotenv—indirect
PyPIragas—indirect
PyPIrank-bm25—indirect
Dependency advisories 2

Installing pypi:ragas@0.4.3 pulls in 90 packages, direct and transitive: 2 carry known advisories, of which 2 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
diskcache5.6.3directmoderate2—
langchain-openai1.1.9directlow21.1.14

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.