Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 18:34 UTC

doctrine / migrations

Doctrine Database Migrations Library

PHPMIT★ 4,768 stars⑂ 393 forkssince Mar 2010View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

doctrine/migrations holds a health index of 87 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (87/100) and lowest on AI Readiness (37/100). It was last updated 69 days ago. 3 contributors account for most of its recent work.

87
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.

87
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 73 is calibrated to 87 on the published index scale (record calibration 2026-08-02).

Ownership

DoctrineOrganization · verified domain
346 followers77 public repossince Feb 2010

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
Packagistdoctrine/migrations3.9.74,441,69790125 days agodatabasedbalmigrations

Metrics by category

Vitality

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

63Moderate · 21% of overall
How it's scored
18/36Push recencylast push 69 days ago
11.8/36Commit cadence17/52 weeks with commits
16.3/18Commit volume64 commits in the last year
5/10OpenSSF Scorecard: Maintained5 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year64
human_commit_share0.7
days_since_last_push69
active_weeks_last_year17
How it's scored
27/27Ships releases89 releases published
27/36Release recencylatest release 125 days ago
19.8/27Release cadencea release every ~62.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count89
latest_release_tag3.9.7
releases_from_tagsno
days_since_latest_release125
mean_days_between_releases62.2
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?

87Excellent · 17% of overall
How it's scored
59.7/60Stars4,768 stars
21.6/25Forks393 forks
8.5/15Watchers35 watchers
Inputs used
forks393
stars4,768
watchers35
growth_stateorganic
growth_factor_pct100
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicescodecov.io, github.com, shields.io
has_pull_request_templateyes
How it's scored
80/80Monthly downloads4,441,697 downloads/month across packagist
18.2/20Registry dependents534 packages depend on it
Inputs used
packagesdoctrine/migrations
dependents534
ecosystemspackagist
total_downloads225,771,633
monthly_downloads4,441,697
unverified_packages_excluded

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

85Excellent · 23% of overall
How it's scored
36/54Bus factor3 contributor(s) cover half of all commits
17.6/22.5Commit distributiontop contributor authored 22% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 84 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled99
top_contributor_share0.218
How it's scored
33.7/42Issue resolution80% of issues closed
24.5/30PR acceptance785/960 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-ReviewFound 2/5 approved changesets -- score normalized to 4
Inputs used
merged_prs785
open_issues119
closed_issues483
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.802
closed_unmerged_prs175
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 backingorganization-owned
20/20Verified domain
18.3/25Owner reach346 followers of doctrine
25/25Track record77 public repos, account ~16 yr old
Inputs used
followers346
owner_typeOrganization
is_verifiedyes
owner_logindoctrine
public_repos77
account_age_days6,029

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on packagist
35/35Publish recencylatest publish 125 days ago
20/20Version history90 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesdoctrine/migrations
ecosystemspackagist
any_deprecatedno
min_days_since_publish125

Engineering Quality

Are baseline engineering and documentation practices in place?

73Good · 19% of overall
How it's scored
24/24CI workflows8 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests17 out of 17 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

80Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://www.doctrine-project.org/projects/migrations.html
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepagehttps://www.doctrine-project.org/projects/migrations.html
docs_sitehttps://www.doctrine-project.org/projects/migrations.html
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

66Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests17 out of 17 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3/7.5Code-ReviewFound 2/5 approved changesets -- score normalized to 4
2.5/2.5Contributorsproject has 84 contributing companies or organizations
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
3.8/7.5Maintained5 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
4.5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated12
scorecard_versionv5.5.0
checks_inconclusive6
scorecard_aggregate6.6
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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.

37Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
33.5/40Legible commit history44 of 70 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.629
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance30 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.3
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codePHP without a type-check config
55/55Manageable file sizes0/297 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes21,851
source_files_sampled297
oversized_source_files0

Key facts

4,768GitHub stars
99contributors
64commits, last 12 months
69days since last push
89releases
3bus factor
119open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-07-03: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 4768 stars today.
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 4,770 ★ / 393 ⇿
4,770Stars
393Forks
89Releases

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.

Star history is shown as collected on 2026-07-03. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

01,0002,0003,0004,0005,0004,770386302010-062018-062026-07
Major 3Minor 20Patch 56

Each point covers 15 days.

OpenSSF Scorecard 6.6 / 10
6.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-27 18:34 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
10CI-Tests17 out of 17 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 2/5 approved changesets -- score normalized to 4
10Contributorsproject has 84 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
5Maintained5 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 7
RegistryPackageVersion constraintManifest
Packagistdoctrine/dbal^3.6 || ^4composer.json
Packagistdoctrine/deprecations^0.5.3 || ^1composer.json
Packagistdoctrine/event-manager^1.2 || ^2.0composer.json
Packagistpsr/log^1.1.3 || ^2 || ^3composer.json
Packagistsymfony/console^5.4 || ^6.0 || ^7.0 || ^8.0composer.json
Packagistsymfony/stopwatch^5.4 || ^6.0 || ^7.0 || ^8.0composer.json
Packagistsymfony/var-exporter^6.2 || ^7.0 || ^8.0composer.json
All dependencies 25

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

RegistryPackageVersionRelation
Packagistdoctrine/dbaldirect
Packagistdoctrine/deprecationsdirect
Packagistdoctrine/event-managerdirect
Packagistpsr/logdirect
Packagistsymfony/consoledirect
Packagistsymfony/stopwatchdirect
Packagistsymfony/var-exporterdirect
Packagistcomposer-runtime-apiindirect
Packagistdoctrine/coding-standardindirect
Packagistdoctrine/docs-builderindirect
Packagistdoctrine/ormindirect
Packagistdoctrine/persistenceindirect
Packagistdoctrine/sql-formatterindirect
Packagistext-pdo_sqliteindirect
Packagistfig/log-testindirect
Packagistphpindirect
Packagistphpstan/phpstanindirect
Packagistphpstan/phpstan-deprecation-rulesindirect
Packagistphpstan/phpstan-phpunitindirect
Packagistphpstan/phpstan-strict-rulesindirect
Packagistphpstan/phpstan-symfonyindirect
Packagistphpunit/phpunitindirect
Packagistsymfony/cacheindirect
Packagistsymfony/processindirect
Packagistsymfony/yamlindirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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 statisticsPackagist.