Public record
Software health reportschema 0.31.0 · metrics 2.5.0 · 2026-08-06 10:07 UTC

dartsim / dart

Research-focused C++23 physics engine for robotics, animation, and machine learning, with Python bindings

C++ · PythonBSD-2-Clause★ 1,191 stars⑂ 303 forkssince Sep 2011View on GitHub ↗

dartsim/dart holds a health index of 90 out of 100, placing it in the Excellent band. It scores highest on Vitality (92/100) and lowest on Security (65/100). It was last updated 1 day ago. A single contributor accounts 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

54 followers16 public repossince Apr 2013

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
PyPIdartpy6.19.4-1618 days agodartsimrobotics

Metrics by category

Vitality

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

92Excellent · 21% of overall
How it's scored
36/36Push recency — last push 1 days ago
29.8/36Commit cadence — 43/52 weeks with commits
18/18Commit volume — 1,420 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,420
human_commit_share0.93
days_since_last_push1
active_weeks_last_year43
How it's scored
27/27Ships releases — 82 releases published
36/36Release recency — latest release 4 days ago
27/27Release cadence — a release every ~6.3 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count82
latest_release_tagverification-media-gui-docking-scale
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases6.3

Community & Adoption

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

79Good · 17% of overall
How it's scored
49.9/60Stars — 1,191 stars
20.7/25Forks — 303 forks
9.4/15Watchers — 50 watchers
Inputs used
forks303
stars1,191
watchers50
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (BSD-2-Clause)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges8
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesapp.codacy.com, codecov.io, github.com, readthedocs.org, shields.io
has_pull_request_templateyes

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.1/22.5Commit distribution — top contributor authored 69% of commits
13.5/13.5Contributor breadth — 52 contributors
10/10OpenSSF Scorecard: Contributors — project has 28 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled52
top_contributor_share0.686
How it's scored
42/42Issue resolution — 100% of issues closed
27.9/30PR acceptance — 2,471/2,659 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/20 approved changesets -- score normalized to 0
Inputs used
merged_prs2,471
open_issues1
closed_issues698
prs_merged_7d21
prs_decided_7d21
prs_merged_30d32
prs_decided_30d33
issue_closed_ratio0.999
closed_unmerged_prs188
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): newcomer_pr_acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
12.5/25Owner reach — 54 followers of dartsim
21/25Track record — 16 public repos, account ~13 yr old
Inputs used
followers54
owner_typeOrganization
is_verified
owner_logindartsim
public_repos16
account_age_days4,857

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

77Good · 19% of overall
How it's scored
24/24CI workflows — 18 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 23 out of 23 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://dart.readthedocs.io
10/10Repository description
10/10Topics — 18 topics
0/10Wiki
Inputs used
topicsrobotics, computer-animation, simulation, kinematics, dynamics, lie-group, inverse-kinematics, urdf, collision-detection, gazebo, mjcf, physics-engine, python-bindings, sdf, multibody, nanobind, rigidbody, cpp23
has_wikino
homepagehttps://dart.readthedocs.io
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

65Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 23 out of 23 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/20 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 28 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
2.5/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
4/5SAST — SAST tool detected but not run on all commits
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate5.6

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_packages1
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:dartpy@6.19.4 runtime dependency closure — what installing the published package pulls in — 1 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.

74Good · 4% of overall
How it's scored
45/45Agent instructions — .agents/AGENTS.md, .codex/AGENTS.md, AGENTS.md, CLAUDE.md, GEMINI.md, dart/collision/AGENTS.md, dart/common/AGENTS.md, dart/constraint/AGENTS.md, dart/dynamics/AGENTS.md, dart/gui/AGENTS.md, dart/io/AGENTS.md, dart/simulation/AGENTS.md, docs/AGENTS.md, docs/background/AGENTS.md, docs/design/AGENTS.md, docs/plans/AGENTS.md, python/AGENTS.md, tests/AGENTS.md
0/15Machine-readable docs (llms.txt)
39.6/40Legible commit history — 69 of 93 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share0.742
agent_instruction_files.agents/AGENTS.md, .codex/AGENTS.md, AGENTS.md, CLAUDE.md, GEMINI.md, dart/collision/AGENTS.md, dart/common/AGENTS.md, dart/constraint/AGENTS.md, dart/dynamics/AGENTS.md, dart/gui/AGENTS.md, dart/io/AGENTS.md, dart/simulation/AGENTS.md, docs/AGENTS.md, docs/background/AGENTS.md, docs/design/AGENTS.md, docs/plans/AGENTS.md, python/AGENTS.md, tests/AGENTS.md
agent_instruction_max_bytes11,896
How it's scored
18/18One-command bootstrap — docs/readthedocs/Makefile
22/22Automated tests
0/11Lint / format config
11/11Static type checking — C++ (statically typed)
10/10Reproducible environment — devcontainer, Dockerfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 1 of the last 100 commits are automated dependency updates
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_languageyes
bootstrap_filesdocs/readthedocs/Makefile
has_devcontaineryes
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.01
How it's scored
45/45Type-checkable code — C++ (statically typed)
53.2/55Manageable file sizes — 78/2,382 source files over 60KB
Inputs used
primary_languageC++
largest_source_bytes2,960,848
source_files_sampled2,382
oversized_source_files78
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examples — demos, examples, notebooks
Inputs used
example_dirsdemos, examples, notebooks
has_mcp_signalno
api_schema_files

Key facts

1,191GitHub stars
52contributors
1,420commits, last 12 months
1days since last push
82releases
1bus 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 ★ / 303 ⇿
0Stars
303Forks
81Releases

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.

05010015020025030029572013-022019-112026-08
Major 2Minor 23Patch 52

Each point covers 13 days.

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).Scorecard v5.5.0 · 2026-08-06 10:07 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests23 out of 23 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/20 approved changesets -- score normalized to 0
10Contributorsproject has 28 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 8 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
8SASTSAST tool detected but not run on all commits
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
PyPInumpypyproject.toml
All dependencies 10

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

RegistryPackageVersionRelation
PyPIjinja2indirect
PyPImyst-parserindirect
PyPInanobindindirect
PyPIpytestindirect
PyPIscikit-build-coreindirect
PyPIsphinxindirect
PyPIsphinx-copybuttonindirect
PyPIsphinx-intlindirect
PyPIsphinx-rtd-themeindirect
PyPIsphinx-tabsindirect
Dependency advisories 0

Installing pypi:dartpy@6.19.4 pulls in 1 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

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.5.0, schema v0.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsPyPI.