datajoint / datajoint-python
Relational Workflows: where database schemas define executable data pipelines.
datajoint/datajoint-python holds a health index of 89 out of 100, placing it in the Excellent band. It scores highest on Vitality (90/100) and lowest on AI Readiness (51/100). It was last updated 5 days ago. A single contributor accounts for most of its recent work.
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.
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 75 is calibrated to 89 on the published index scale (record calibration 2026-08-02).
Ownership
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 |
|---|---|---|---|---|---|---|
| PyPI | datajoint | 2.3.3 | - | 85 | 5 days ago | data-engineeringdata-integritydata-lineagedata-pipelinesdatajointdeclarativeetlmysqlneuroscienceobject-storagepostgresqlrelational-modelreproducibilityresearch-softwareschema-managementscientific-computingworkflow-management |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
Development activity
How it's scored
| 36/36 | Push recency — last push 5 days ago |
| 25.6/36 | Commit cadence — 37/52 weeks with commits |
| 18/18 | Commit volume — 842 commits in the last year |
| 10/10 | OpenSSF Scorecard: Maintained — 30 commit(s) and 29 issue activity found in the last 90 days -- score normalized to 10 |
Inputs used
| commits_last_year | 842 |
| human_commit_share | 1 |
| days_since_last_push | 5 |
| active_weeks_last_year | 37 |
Release discipline
How it's scored
| 27/27 | Ships releases — 58 releases published |
| 36/36 | Release recency — latest release 5 days ago |
| 27/27 | Release cadence — a release every ~22.7 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases. |
Inputs used
| releases_count | 58 |
| latest_release_tag | v2.3.3 |
| releases_from_tags | no |
| days_since_latest_release | 5 |
| mean_days_between_releases | 22.7 |
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
Popularity & adoption
How it's scored
| 37.2/60 | Stars — 197 stars |
| 16.6/25 | Forks — 98 forks |
| 5.6/15 | Watchers — 11 watchers |
Inputs used
| forks | 98 |
| stars | 197 |
| watchers | 11 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (Apache-2.0) |
| 18/18 | CONTRIBUTING guide |
| 0/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 0/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | yes |
| readme_badges | 6 |
| has_contributing | yes |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | coveralls.io, github.com, shields.io |
| has_pull_request_template | no |
Sustainability & Governance
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
How it's scored
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 11/22.5 | Commit distribution — top contributor authored 51% of commits |
| 13.5/13.5 | Contributor breadth — 40 contributors |
| 10/10 | OpenSSF Scorecard: Contributors — project has 66 contributing companies or organizations |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 40 |
| top_contributor_share | 0.509 |
Issue & PR responsiveness
How it's scored
| 41.4/42 | Issue resolution — 98% of issues closed |
| 26.7/30 | PR acceptance — 718/807 decided PRs merged |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 15/15 | OpenSSF Scorecard: Code-Review — all changesets reviewed |
Inputs used
| merged_prs | 718 |
| open_issues | 11 |
| closed_issues | 711 |
| prs_merged_7d | 3 |
| prs_decided_7d | 3 |
| prs_merged_30d | 6 |
| prs_decided_30d | 6 |
| issue_closed_ratio | 0.985 |
| closed_unmerged_prs | 89 |
| first_time_authors_30d | 0 |
| first_time_prs_merged_30d | 0 |
| first_time_prs_decided_30d | 0 |
Ownership & stewardship
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 20/20 | Verified domain |
| 13.5/25 | Owner reach — 74 followers of datajoint |
| 25/25 | Track record — 92 public repos, account ~13 yr old |
Inputs used
| followers | 74 |
| owner_type | Organization |
| is_verified | yes |
| owner_login | datajoint |
| public_repos | 92 |
| account_age_days | 5,109 |
Package maintenance
How it's scored
| 25/25 | Published & resolvable — 1 package(s) on pypi |
| 35/35 | Publish recency — latest publish 5 days ago |
| 20/20 | Version history — 85 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | datajoint |
| ecosystems | pypi |
| any_deprecated | no |
| min_days_since_publish | 5 |
Engineering Quality
Are baseline engineering and documentation practices in place?
Engineering practices
How it's scored
| 24/24 | CI workflows — 5 workflow(s) |
| 24/24 | Tests present |
| 16/16 | Linter config — pyproject.toml ([tool.ruff]) |
| 9.6/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 0/20 | OpenSSF Scorecard: CI-Tests — no data |
Inputs used
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | yes |
| has_precommit_config | yes |
Documentation
How it's scored
| 30/30 | README |
| 0/25 | Documentation directory |
| 15/15 | Documentation / homepage site — https://docs.datajoint.com |
| 10/10 | Repository description |
| 10/10 | Topics — 17 topics |
| 0/10 | Wiki |
Inputs used
| topics | datajoint, scientific-computing, python, relational-model, mysql, data-pipelines, workflow-management, data-engineering, data-integrity, data-lineage, declarative, metadata-management, object-storage, postgresql, reproducibility, research-software, data-provenance |
| has_wiki | no |
| homepage | https://docs.datajoint.com |
| docs_site | https://docs.datajoint.com |
| has_readme | yes |
| has_docs_dir | no |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
Security posture
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — no data |
| 0/2.5 | CI-Tests — no data |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 7.5/7.5 | Code-Review — all changesets reviewed |
| 2.5/2.5 | Contributors — project has 66 contributing companies or organizations |
| 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.5/2.5 | License — license file detected |
| 7.5/7.5 | Maintained — 30 commit(s) and 29 issue activity found in the last 90 days -- score normalized to 10 |
| 0/5 | Packaging — no data |
| 0/5 | Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
| 0/5 | SAST — no data |
| 0/5 | Security-Policy — security policy file not detected |
| 0/7.5 | Signed-Releases — Project has not signed or included provenance with any releases. |
| 0/7.5 | Token-Permissions — detected GitHub workflow tokens with excessive permissions |
| 7.5/7.5 | Vulnerabilities — 0 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 14 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 4 |
| scorecard_aggregate | 6.2 |
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.
Agent context & guidance
How it's scored
| 0/45 | Agent instructions — no CLAUDE.md / AGENTS.md / editor rules |
| 15/15 | Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.datajoint.com/llms.txt) |
| 40/40 | Legible commit history — 90 of 100 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | yes |
| llms_txt_url | https://docs.datajoint.com/llms.txt |
| legible_history_share | 0.9 |
| agent_instruction_files | — |
| agent_instruction_max_bytes | — |
How it's scored
| 0/18 | One-command bootstrap |
| 22/22 | Automated tests |
| 11/11 | Lint / format config — pyproject.toml ([tool.ruff]) |
| 0/11 | Static type checking |
| 10/10 | Reproducible environment — Dockerfile |
| 0/10 | Demonstrated agent practice — no agent-authored commits among the last 100 |
| 5/8 | Automated maintenance — dependency automation configured, none observed in the sampled commits |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | — |
| has_dockerfile | yes |
| typed_language | no |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | yes |
| typecheck_configs | — |
| agent_commit_share | 0 |
| toolchain_manifests | — |
| dependency_bot_commit_share | 0 |
Code legibility for models
How it's scored
| 0/45 | Type-checkable code — Python without a type-check config |
| 53.3/55 | Manageable file sizes — 4/133 source files over 60KB |
Inputs used
| primary_language | Python |
| largest_source_bytes | 91,166 |
| source_files_sampled | 133 |
| oversized_source_files | 4 |
Key facts
Data collection warnings
- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
- pypi download statistics for 'datajoint' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced
- OSV advisory lookup failed: [Errno 101] Network is unreachable
More detail
Star and fork history 0 ★ / 98 ⇿
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.
Each point covers 11 days.
OpenSSF Scorecard 6.2 / 10
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 |
| n/a | Branch-Protection | internal 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 |
| n/a | CI-Tests | internal error: internal error: Client.Repositories.ListCheckRunsForRef: error during graphqlHandler.setupCheckRuns: Something went wrong while executing your query on 2026-09-15T15:02:11Z. Please include `DB22:268D3D:73DC3D:706A2C:6AA95DEF` when reporting this issue. |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 10 | Code-Review | all changesets reviewed |
| 10 | Contributors | project has 66 contributing companies or organizations |
| 10 | Dangerous-Workflow | no dangerous workflow patterns detected |
| 10 | Dependency-Update-Tool | update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 10 | Maintained | 30 commit(s) and 29 issue activity found in the last 90 days -- score normalized to 10 |
| n/a | Packaging | packaging workflow not detected |
| 0 | Pinned-Dependencies | dependency not pinned by hash detected -- score normalized to 0 |
| n/a | SAST | internal error: internal error: Client.Checks.ListCheckRunsForRef: error during graphqlHandler.setupCheckRuns: Something went wrong while executing your query on 2026-09-15T15:02:11Z. Please include `DB22:268D3D:73DC3D:706A2C:6AA95DEF` when reporting this issue. |
| 0 | Security-Policy | security policy file not detected |
| 0 | Signed-Releases | Project has not signed or included provenance with any releases. |
| 0 | Token-Permissions | detected GitHub workflow tokens with excessive permissions |
| 10 | Vulnerabilities | 0 existing vulnerabilities detected |
Direct dependencies 11
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| PyPI | numpy | — | pyproject.toml |
| PyPI | pymysql | >=0.7.2 | pyproject.toml |
| PyPI | deepdiff | — | pyproject.toml |
| PyPI | pyparsing | — | pyproject.toml |
| PyPI | pandas | — | pyproject.toml |
| PyPI | tqdm | — | pyproject.toml |
| PyPI | networkx | — | pyproject.toml |
| PyPI | pydot | — | pyproject.toml |
| PyPI | fsspec | >=2023.1.0 | pyproject.toml |
| PyPI | pydantic-settings | >=2.0.0 | pyproject.toml |
| PyPI | packaging | — | pyproject.toml |
All dependencies 10
Full resolved dependency set from the GitHub dependency graph: 3 direct and 7 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
| Registry | Package | Version | Relation |
|---|---|---|---|
| PyPI | fsspec | — | direct |
| PyPI | pydantic-settings | — | direct |
| PyPI | pymysql | — | direct |
| PyPI | adlfs | — | indirect |
| PyPI | gcsfs | — | indirect |
| PyPI | polars | — | indirect |
| PyPI | psycopg2-binary | — | indirect |
| PyPI | pyarrow | — | indirect |
| PyPI | s3fs | — | indirect |
| PyPI | testcontainers | — | indirect |
Dependency advisories not assessed
Advisory matching could not run for this report: OSV advisory lookup failed: [Errno 101] Network is unreachable
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 — PyPI.