Public recordGood
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-18 22:08 UTC
Precisa-Saude / medbench-brasil
Leaderboard reproduzível de LLMs em provas médicas brasileiras (Revalida, INEP) — zero-shot, 3 execuções, análise de contaminação
Precisa-Saude/medbench-brasil holds a health index of 77 out of 100, placing it in the Good band. It scores highest on Engineering Quality (94/100) and lowest on Community & Adoption (45/100). It was last updated 8 days ago. A single contributor accounts for most of its recent work.
77
overall / 100Software 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.
77
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)
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 66 is calibrated to 77 on the published index scale (record calibration 2026-08-02).
Ownership
Precisa SaúdeOrganization
5 followers10 public repossince Jan 2026
This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.
Package ecosystems
| Registry | Package | Version | Downloads / mo | Versions | Last publish | Tags |
|---|---|---|---|---|---|---|
| npm | @precisa-saude/medbench-dataset | 2.3.0 | 1,296 | 18 | 17 days ago | revalidamedical-examsbrazilllm-benchmarkdataset |
| npm | @precisa-saude/medbench-harness | 2.3.0 | 1,257 | 18 | 17 days ago | llmbenchmarkevaluationmedicalbrazilrevalida |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
79
Development activity
65Good
How it's scored
| 28.8/36 | Push recency — last push 8 days ago |
| 8.3/36 | Commit cadence — 12/52 weeks with commits |
| 18/18 | Commit volume — 148 commits in the last year |
| 10/10 | OpenSSF Scorecard: Maintained — 30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10 |
Inputs used
| commits_last_year | 148 |
| human_commit_share | 0.99 |
| days_since_last_push | 8 |
| active_weeks_last_year | 12 |
Release discipline
100Exceptional
How it's scored
| 27/27 | Ships releases — 18 releases published |
| 36/36 | Release recency — latest release 17 days ago |
| 27/27 | Release cadence — a release every ~12.5 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 18 |
| latest_release_tag | v2.3.0 |
| releases_from_tags | no |
| days_since_latest_release | 17 |
| mean_days_between_releases | 12.5 |
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?
45
Popularity & adoption
1Critical
How it's scored
| 0/60 | Stars — 2 stars |
| 0/25 | Forks — 1 forks |
| 0/15 | Watchers — 0 watchers |
Inputs used
| forks | 1 |
| stars | 2 |
| watchers | 0 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
86Excellent
How it's scored
| 22.5/22.5 | README |
| 16.9/22.5 | License — license file present, not a recognized license |
| 18/18 | CONTRIBUTING guide |
| 13.5/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 6.3/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | yes |
| readme_badges | 1 |
| has_contributing | yes |
| has_issue_template | no |
| has_code_of_conduct | yes |
| readme_badge_services | shields.io |
| has_pull_request_template | yes |
Ecosystem adoption (downloads)
57Moderate
How it's scored
| 45.4/80 | Monthly downloads — 2,553 downloads/month across npm |
| 0/20 | Registry dependents — not reported by this ecosystem |
Inputs used
| packages | @precisa-saude/medbench-dataset, @precisa-saude/medbench-harness |
| dependents | — |
| ecosystems | npm |
| total_downloads | — |
| monthly_downloads | 2,553 |
| 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?
53
Maintainer resilience (bus factor)
24At Risk
How it's scored
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 2.7/22.5 | Commit distribution — top contributor authored 88% of commits |
| 2.7/13.5 | Contributor breadth — 2 contributors |
| 10/10 | OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10 |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 2 |
| top_contributor_share | 0.878 |
Issue & PR responsiveness
59Moderate
How it's scored
| 30.5/42 | Issue resolution — 73% of issues closed |
| 28.8/30 | PR acceptance — 72/75 decided PRs merged |
| 0/13 | Newcomer PR acceptance — 0/1 first-time contributors' PRs merged in 30d |
| 0/15 | OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0 |
Inputs used
| merged_prs | 72 |
| open_issues | 3 |
| closed_issues | 8 |
| prs_merged_7d | 0 |
| prs_decided_7d | 0 |
| prs_merged_30d | 21 |
| prs_decided_30d | 22 |
| issue_closed_ratio | 0.727 |
| closed_unmerged_prs | 3 |
| first_time_authors_30d | 1 |
| first_time_prs_merged_30d | 0 |
| first_time_prs_decided_30d | 1 |
Ownership & stewardship
45Weak
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 0/20 | Verified domain |
| 5.6/25 | Owner reach — 5 followers of Precisa-Saude |
| 9.2/25 | Track record — 10 public repos, account ~0 yr old |
Inputs used
| followers | 5 |
| owner_type | Organization |
| is_verified | no |
| owner_login | Precisa-Saude |
| public_repos | 10 |
| account_age_days | 288 |
Package maintenance
100Exceptional
How it's scored
| 25/25 | Published & resolvable — 2 package(s) on npm |
| 35/35 | Publish recency — latest publish 17 days ago |
| 20/20 | Version history — 18 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | @precisa-saude/medbench-dataset, @precisa-saude/medbench-harness |
| ecosystems | npm |
| any_deprecated | no |
| min_days_since_publish | 17 |
Engineering Quality
Are baseline engineering and documentation practices in place?
94
Engineering practices
90Excellent
How it's scored
| 24/24 | CI workflows — 5 workflow(s) |
| 24/24 | Tests present |
| 16/16 | Linter config — eslint.config.js |
| 0/9.6 | Pre-commit hooks |
| 6.4/6.4 | .editorconfig |
| 20/20 | OpenSSF Scorecard: CI-Tests — 23 out of 23 merged PRs checked by a CI test -- score normalized to 10 |
Inputs used
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | yes |
| has_linter_config | yes |
| has_precommit_config | no |
Documentation
100Exceptional
How it's scored
| 30/30 | README |
| 25/25 | Documentation directory |
| 15/15 | Documentation / homepage site — https://medbench-brasil.ia.br |
| 10/10 | Repository description |
| 10/10 | Topics — 19 topics |
| 10/10 | Wiki |
Inputs used
| topics | brazil, brazilian-portuguese, contamination-detection, healthcare-ai, inep, leaderboard, llm-benchmark, llm-evaluation, medical-ai, medical-education, medical-llm, monorepo, open-source, portuguese, reproducible-research, typescript, zero-shot, enamed, revalida |
| has_wiki | yes |
| homepage | https://medbench-brasil.ia.br |
| docs_site | https://medbench-brasil.ia.br |
| has_readme | yes |
| has_docs_dir | yes |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
56
Security posture
56Moderate
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — branch protection not enabled on development/release branches |
| 2.5/2.5 | CI-Tests — 23 out of 23 merged PRs checked by a CI test -- score normalized to 10 |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 0/7.5 | Code-Review — Found 0/30 approved changesets -- score normalized to 0 |
| 2.5/2.5 | Contributors — project has 3 contributing companies or organizations -- score normalized to 10 |
| 10/10 | Dangerous-Workflow — no dangerous workflow patterns detected |
| 7.5/7.5 | Dependency-Update-Tool — update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.2/2.5 | License — license file detected |
| 7.5/7.5 | Maintained — 30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10 |
| 5/5 | Packaging — packaging workflow detected |
| 5/5 | Pinned-Dependencies — all dependencies are pinned |
| 0/5 | SAST — SAST tool is not run on all commits -- score normalized to 0 |
| 5/5 | Security-Policy — security policy file detected |
| 0/7.5 | Signed-Releases — no data |
| 0/7.5 | Token-Permissions — detected GitHub workflow tokens with excessive permissions |
| 0/7.5 | Vulnerabilities — 118 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 17 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 1 |
| scorecard_aggregate | 5.6 |
Excluded from scoring (no data or not applicable): Signed-Releases. Remaining weights renormalized.
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.
81
Agent context & guidance
85Excellent
How it's scored
| 45/45 | Agent instructions — AGENTS.md, CLAUDE.md |
| 0/15 | Machine-readable docs (llms.txt) |
| 40/40 | Legible commit history — 98 of 99 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | 0.99 |
| agent_instruction_files | AGENTS.md, CLAUDE.md |
| agent_instruction_max_bytes | 3,959 |
Verify loop (build / test / typecheck)
64Moderate
How it's scored
| 0/18 | One-command bootstrap |
| 22/22 | Automated tests |
| 11/11 | Lint / format config — eslint.config.js |
| 11/11 | Static type checking — packages/dataset/tsconfig.json, packages/eval-harness/tsconfig.json, packages/ingestion/tsconfig.json, site/tsconfig.json, tsconfig.json |
| 10/10 | Reproducible environment — lockfile |
| 0/10 | Demonstrated agent practice — no agent-authored commits among the last 100 |
| 0/8 | Automated maintenance — no automated dependency updates observed |
| 10/10 | OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | pnpm-lock.yaml |
| has_dockerfile | no |
| typed_language | yes |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | yes |
| typecheck_configs | packages/dataset/tsconfig.json, packages/eval-harness/tsconfig.json, packages/ingestion/tsconfig.json, site/tsconfig.json, tsconfig.json |
| agent_commit_share | 0 |
| toolchain_manifests | — |
| dependency_bot_commit_share | 0 |
Code legibility for models
100Exceptional
How it's scored
| 45/45 | Type-checkable code — TypeScript (statically typed) |
| 55/55 | Manageable file sizes — 0/135 source files over 60KB |
Inputs used
| primary_language | TypeScript |
| largest_source_bytes | 20,192 |
| source_files_sampled | 135 |
| oversized_source_files | 0 |
Machine-readable interfaces
100Exceptional
How it's scored
| 0/40 | API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software |
| 0/20 | MCP server — not applicable to this kind of software |
| 40/40 | Runnable examples — examples |
Inputs used
| example_dirs | examples |
| has_mcp_signal | no |
| 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
2GitHub stars
2contributors
148commits, last 12 months
8days since last push
18releases
1bus factor
3open issues
npmpackage ecosystems
Data collection warnings
- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
- GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
More detail
OpenSSF Scorecard 5.6 / 10
5.6aggregate
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).
| 10 | Binary-Artifacts | no binaries found in the repo |
| 0 | Branch-Protection | branch protection not enabled on development/release branches |
| 10 | CI-Tests | 23 out of 23 merged PRs checked by a CI test -- score normalized to 10 |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 0 | Code-Review | Found 0/30 approved changesets -- score normalized to 0 |
| 10 | Contributors | project has 3 contributing companies or organizations -- score normalized to 10 |
| 10 | Dangerous-Workflow | no dangerous workflow patterns detected |
| 10 | Dependency-Update-Tool | update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 9 | License | license file detected |
| 10 | Maintained | 30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10 |
| 10 | Packaging | packaging workflow detected |
| 10 | Pinned-Dependencies | all dependencies are pinned |
| 0 | SAST | SAST tool is not run on all commits -- score normalized to 0 |
| 10 | Security-Policy | security policy file detected |
| n/a | Signed-Releases | no releases found |
| 0 | Token-Permissions | detected GitHub workflow tokens with excessive permissions |
| 0 | Vulnerabilities | 118 existing vulnerabilities detected |
Direct dependencies 19
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| npm | @precisa-saude/medbench-dataset | workspace:* | site/package.json |
| npm | @precisa-saude/medbench-harness | workspace:* | site/package.json |
| npm | @precisa-saude/themes | ^1.6.0 | site/package.json |
| npm | @precisa-saude/ui | ^1.6.0 | site/package.json |
| npm | @radix-ui/react-tooltip | ^1.2.8 | site/package.json |
| npm | class-variance-authority | ^0.7.1 | site/package.json |
| npm | clsx | ^2.1.1 | site/package.json |
| npm | lucide-react | ^0.562.0 | site/package.json |
| npm | react | ^19.0.0 | site/package.json |
| npm | react-dom | ^19.0.0 | site/package.json |
| npm | react-router-dom | ^7.1.0 | site/package.json |
| npm | recharts | ^2.15.0 | site/package.json |
| npm | tailwind-merge | ^3.5.0 | site/package.json |
| npm | tw-animate-css | ^1.4.0 | site/package.json |
| npm | @precisa-saude/medbench-dataset | workspace:* | packages/eval-harness/package.json |
| npm | dotenv | ^17.4.2 | packages/eval-harness/package.json |
| npm | @aws-sdk/client-bedrock-runtime | ^3.1032.0 | packages/ingestion/package.json |
| npm | @kreuzberg/node | ^4.0.8 | packages/ingestion/package.json |
| npm | @precisa-saude/medbench-dataset | workspace:* | packages/ingestion/package.json |
All dependencies not collected
The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
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.
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 — npm.