Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-27 06:05 UTC

mims-harvard / ToolUniverse

Democratizing AI scientists with ToolUniverse

PythonApache-2.0★ 1,705 stars⑂ 258 forkssince Mar 2025View on GitHub ↗
KindMCP serverCommand-line toolLibraryNetwork servicehow this is determined

mims-harvard/ToolUniverse 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 Security (25/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

856 followers77 public repossince Feb 2020

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPItooluniverse1.5.431,873820 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
32.5/36Commit cadence — 47/52 weeks with commits
18/18Commit volume — 1,031 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year1,031
human_commit_share0.99
days_since_last_push0
active_weeks_last_year47

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 68 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~11.6 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count68
latest_release_tagv1.5.4
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases11.6

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

71Good · 17% of overall
How it's scored
52.4/60Stars — 1,705 stars
20.1/25Forks — 258 forks
7/15Watchers — 19 watchers
Inputs used
forks258
stars1,705
watchers19
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)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges9
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, shields.io
has_pull_request_templateyes
How it's scored
60/80Monthly downloads — 31,873 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagestooluniverse
dependents—
ecosystemspypi
total_downloads—
monthly_downloads31,873
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
2.7/22.5Commit distribution — top contributor authored 88% of commits
13.5/13.5Contributor breadth — 27 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled27
top_contributor_share0.878
How it's scored
37.5/42Issue resolution — 89% of issues closed
18.6/30PR acceptance — 358/578 decided PRs merged
13/13Newcomer PR acceptance — 5/5 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs358
open_issues8
closed_issues66
prs_merged_7d49
prs_decided_7d52
prs_merged_30d57
prs_decided_30d60
issue_closed_ratio0.892
closed_unmerged_prs220
first_time_authors_30d3
first_time_prs_merged_30d5
first_time_prs_decided_30d5
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
21.1/25Owner reach — 856 followers of mims-harvard
25/25Track record — 77 public repos, account ~6 yr old
Inputs used
followers856
owner_typeOrganization
is_verifiedno
owner_loginmims-harvard
public_repos77
account_age_days2,425

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 — 82 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagestooluniverse
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

91Excellent · 19% of overall
How it's scored
24/24CI workflows — 11 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.ruff])
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

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://aiscientist.tools
10/10Repository description
10/10Topics — 16 topics
0/10Wiki
Inputs used
topicsagents, reasoning-agent, reasoning-language-models, tool-use, ai-agents, ai-scientists, automated-science, co-pilot, co-scientist, ai-for-science, autonomous-agents, llms, lrm, ai-communication, mcp-servers, scientific-skill
has_wikino
homepagehttps://aiscientist.tools
docs_sitehttps://aiscientist.tools
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

25At Risk · 16% of overall
How it's scored
0/30Security policy (SECURITY.md)
0/25Dependabot config
25/25Dependency lockfiles — uv.lock
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfilesuv.lock
manifestsdocs/requirements.txt, docs/requirements_themes.txt, mcpb/pyproject.toml, pyproject.toml
has_codeql_workflowno
has_security_policyno
has_dependabot_configno

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.

61Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 95 of 99 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.96
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — docs/Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.ruff])
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
10/10Demonstrated agent practice — 6 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileyes
typed_languageno
bootstrap_filesdocs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.06
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
54.7/55Manageable file sizes — 25/5,039 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes6,009,537
source_files_sampled5,039
oversized_source_files25
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
20/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalyes
api_schema_files—
interfaces_expected_ofnetwork-service

Key facts

1,705GitHub stars
27contributors
1,031commits, last 12 months
0days since last push
68releases
1bus factor
8open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Could not fetch pypi package 'tooluniverse-mcpb-native' from its registry
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
  • deps.dev does not index pypi:tooluniverse@1.5.4; advisories assessed against the repository dependency graph instead
  • OpenSSF Scorecard did not return a usable result (killed by SIGKILL — most likely the container's memory limit; 2026/09/27 06:04:45 Warning: PATs stored in env variables GITHUB_AUTH_TOKEN and GITHUB_TOKEN differ. Scorecard will use the former.); skipping Scorecard checks

More detail

Star and fork history 0 ★ / 258 ⇿
0Stars
258Forks
67Releases

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.

050100150200250300254102025-032025-122026-09
Major 0Minor 3Patch 32

Each point covers 2 days.

Direct dependencies 26
RegistryPackageVersion constraintManifest
PyPItooluniverse>=1.5.3,<2mcpb/pyproject.toml
PyPIrequests>=2.32.0pyproject.toml
PyPIboltz-api>=0.46.0,<0.47.0pyproject.toml
PyPInumpy>=2.2.0pyproject.toml
PyPIgraphql-core>=3.2.0pyproject.toml
PyPIfastapi>=0.116.0pyproject.toml
PyPIuvicorn>=0.36.0pyproject.toml
PyPIpydantic>=2.11.0pyproject.toml
PyPIpyyaml>=6.0.0pyproject.toml
PyPImcp>=1.29.0,<2.0.0pyproject.toml
PyPIfastmcp>=3.4.5,<4.0.0pyproject.toml
PyPIxmltodict>=1.0.0pyproject.toml
PyPIlxml>=6.0.0pyproject.toml
PyPIhuggingface_hub>=0.34.0pyproject.toml
PyPIjsonpath-ng>=1.6.0pyproject.toml
PyPIrcsb-api>=1.4.0pyproject.toml
PyPIwebsockets>=13.0pyproject.toml
PyPIurllib3>=1.26pyproject.toml
PyPIpandas>=2.2.3pyproject.toml
PyPIopenpyxl>=3.1.0pyproject.toml
PyPIpdfplumber>=0.11.0pyproject.toml
PyPIfaiss-cpu==1.12.0pyproject.toml
PyPIbeautifulsoup4>=4.12.0pyproject.toml
PyPIpython-dotenv>=1.0.0pyproject.toml
PyPIpip>=25.3pyproject.toml
PyPIjsonschema>=4.23.0pyproject.toml
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.

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.