Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 17:54 UTC

doctrine / orm

Doctrine Object Relational Mapper (ORM)

PHPMIT★ 10,170 stars⑂ 2,541 forkssince Apr 2010View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

doctrine/orm holds a health index of 98 out of 100, placing it in the Exceptional band. It scores highest on Vitality (98/100) and lowest on AI Readiness (53/100). It was last updated 1 day ago. 3 contributors account for most of its recent work.

98
overall / 100
Exceptional

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.

98
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 87 is calibrated to 98 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/orm3.6.85,390,96319521 days agodatabaseorm

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 recencylast push 1 days ago
31.8/36Commit cadence46/52 weeks with commits
18/18Commit volume321 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 13 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year321
human_commit_share0.96
days_since_last_push1
active_weeks_last_year46

Release discipline

100Exceptional
How it's scored
27/27Ships releases100 releases published
36/36Release recencylatest release 21 days ago
27/27Release cadencea release every ~13.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count100
latest_release_tag3.6.8
releases_from_tagsno
days_since_latest_release21
mean_days_between_releases13.9
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?

89Excellent · 17% of overall
How it's scored
60/60Stars10,170 stars
25/25Forks2,541 forks
13.2/15Watchers241 watchers
Inputs used
forks2,541
stars10,170
watchers241
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
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
80/80Monthly downloads5,390,963 downloads/month across packagist
20/20Registry dependents7,585 packages depend on it
Inputs used
packagesdoctrine/orm
dependents7,585
ecosystemspackagist
total_downloads310,646,723
monthly_downloads5,390,963
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.4/22.5Commit distributiontop contributor authored 22% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 105 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled99
top_contributor_share0.225
How it's scored
33.6/42Issue resolution80% of issues closed
20.6/30PR acceptance3,968/5,773 decided PRs merged
8.7/13Newcomer PR acceptance2/3 first-time contributors' PRs merged in 30d
13.5/15OpenSSF Scorecard: Code-ReviewFound 12/13 approved changesets -- score normalized to 9
Inputs used
merged_prs3,968
open_issues1,280
closed_issues5,164
prs_merged_7d14
prs_decided_7d16
prs_merged_30d30
prs_decided_30d35
issue_closed_ratio0.801
closed_unmerged_prs1,805
first_time_authors_30d3
first_time_prs_merged_30d2
first_time_prs_decided_30d3
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 21 days ago
20/20Version history195 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesdoctrine/orm
ecosystemspackagist
any_deprecatedno
min_days_since_publish21

Engineering Quality

Are baseline engineering and documentation practices in place?

85Excellent · 19% of overall
How it's scored
24/24CI workflows9 workflow(s)
24/24Tests present
16/16Linter configphpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests13 out of 14 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

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

Security

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

82Excellent · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.2/2.5CI-Tests13 out of 14 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6.8/7.5Code-ReviewFound 12/13 approved changesets -- score normalized to 9
2.5/2.5Contributorsproject has 105 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
7.5/7.5Maintained30 commit(s) and 13 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
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_aggregate7.8
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages1
unassessed_packages22
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 1 resolved dependencies against OSV. 22 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. 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.

53Moderate · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
34.4/40Legible commit history62 of 96 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.646
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configphpstan.neon
0/11Static type checking
0/10Reproducible environment
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance4 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_configyes
typecheck_configs
agent_commit_share0.01
toolchain_manifests
dependency_bot_commit_share0.04
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
54.7/55Manageable file sizes9/1,484 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes124,066
source_files_sampled1,484
oversized_source_files9
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplescookbook
Inputs used
example_dirscookbook
has_mcp_signalno
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

10,170GitHub stars
99contributors
321commits, last 12 months
1days since last push
100releases
3bus factor
1,280open 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-21: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 10170 stars today.

More detail

Star and fork history 10,169 ★ / 2,541 ⇿
10,169Stars
2,541Forks
100Releases

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

02,0004,0006,0008,00010,00012,00010,1692,541192018-062022-072026-08
Major 1Minor 14Patch 82

Each point covers 8 days.

OpenSSF Scorecard 7.8 / 10
7.8aggregate

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 17:54 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
9CI-Tests13 out of 14 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
9Code-ReviewFound 12/13 approved changesets -- score normalized to 9
10Contributorsproject has 105 contributing companies or organizations
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 13 issue activity found in the last 90 days -- score normalized to 10
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 11
RegistryPackageVersion constraintManifest
Packagistdoctrine/collections^2.2composer.json
Packagistdoctrine/dbal^3.8.2 || ^4composer.json
Packagistdoctrine/deprecations^0.5.3 || ^1composer.json
Packagistdoctrine/event-manager^1.2 || ^2composer.json
Packagistdoctrine/inflector^1.4 || ^2.0composer.json
Packagistdoctrine/instantiator^1.3 || ^2composer.json
Packagistdoctrine/lexer^3composer.json
Packagistdoctrine/persistence^3.3.1 || ^4composer.json
Packagistpsr/cache^1 || ^2 || ^3composer.json
Packagistsymfony/console^5.4 || ^6.0 || ^7.0 || ^8.0composer.json
Packagistsymfony/var-exporter^6.3.9 || ^7.0 || ^8.0composer.json
All dependencies 23

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

RegistryPackageVersionRelation
Packagistdoctrine/collectionsdirect
Packagistdoctrine/dbaldirect
Packagistdoctrine/deprecationsdirect
Packagistdoctrine/event-managerdirect
Packagistdoctrine/inflectordirect
Packagistdoctrine/instantiatordirect
Packagistdoctrine/lexerdirect
Packagistdoctrine/persistencedirect
Packagistpsr/cachedirect
Packagistsymfony/consoledirect
Packagistsymfony/var-exporterdirect
Packagistcomposer-runtime-apiindirect
Packagistdoctrine/coding-standardindirect
Packagistdoctrine/docs-builderindirect
Packagistext-ctypeindirect
Packagistphpindirect
Packagistphpbench/phpbenchindirect
Packagistphpstan/extension-installerindirect
Packagistphpstan/phpstan2.1.23indirect
Packagistphpstan/phpstan-deprecation-rulesindirect
Packagistphpunit/phpunitindirect
Packagistpsr/logindirect
Packagistsymfony/cacheindirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 1 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 22 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

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

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.