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

doctrine / annotations

Annotations Docblock Parser

PHPMIT★ 6,731 stars⑂ 233 forkssince Jan 2013View on GitHub ↗

doctrine/annotations holds a health index of 19 out of 100, placing it in the Critical band. It scores highest on Community & Adoption (85/100) and lowest on Vitality (28/100). It was last updated 259 days ago. 5 contributors account for most of its recent work.

19
overall / 100
Critical

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.

19
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 61 is calibrated to 67 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/annotations⚠ deprecated2.0.26,308,17143721 days agoannotationsparserdocblock

Metrics by category

Vitality

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

28At Risk · 21% of overall
How it's scored
3.6/36Push recencylast push 259 days ago
2.1/36Commit cadence3/52 weeks with commits
6.3/18Commit volume4 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year4
human_commit_share1
days_since_last_push259
active_weeks_last_year3
How it's scored
27/27Ships releases38 releases published
7.2/36Release recencylatest release 721 days ago
12.6/27Release cadencea release every ~125.2 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count38
latest_release_tag2.0.2
releases_from_tagsno
days_since_latest_release721
mean_days_between_releases125.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?

85Excellent · 17% of overall
How it's scored
60/60Stars6,731 stars
19.7/25Forks233 forks
8.7/15Watchers37 watchers
Inputs used
forks233
stars6,731
watchers37
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
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_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, poser.pugx.org, shields.io
has_pull_request_templateno
How it's scored
80/80Monthly downloads6,308,171 downloads/month across packagist
20/20Registry dependents2,253 packages depend on it
Inputs used
packagesdoctrine/annotations
dependents2,253
ecosystemspackagist
total_downloads585,969,459
monthly_downloads6,308,171
unverified_packages_excluded

Sustainability & Governance

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

80Excellent · 23% of overall
How it's scored
45.9/54Bus factor5 contributor(s) cover half of all commits
19.2/22.5Commit distributiontop contributor authored 15% of commits
13.5/13.5Contributor breadth100 contributors
10/10OpenSSF Scorecard: Contributorsproject has 76 contributing companies or organizations
Inputs used
bus_factor5
contributors_sampled100
top_contributor_share0.148
How it's scored
34.4/42Issue resolution82% of issues closed
21.5/30PR acceptance260/362 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
9/15OpenSSF Scorecard: Code-ReviewFound 12/19 approved changesets -- score normalized to 6
Inputs used
merged_prs260
open_issues26
closed_issues117
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.818
closed_unmerged_prs102
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
How it's scored
25/25Published & resolvable1 package(s) on packagist
14/35Publish recencylatest publish 721 days ago
20/20Version history43 published versions
0/20Not deprecateddoctrine/annotations: deprecated/yanked on the registry
Inputs used
packagesdoctrine/annotations
ecosystemspackagist
any_deprecatedyes
min_days_since_publish721

Engineering Quality

Are baseline engineering and documentation practices in place?

76Good · 19% of overall
How it's scored
24/24CI workflows6 workflow(s)
24/24Tests present
16/16Linter configphpstan.neon
0/9.6Pre-commit hooks
0/6.4.editorconfig
2/20OpenSSF Scorecard: CI-Tests2 out of 17 merged PRs checked by a CI test -- score normalized to 1
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/annotations.html
10/10Repository description
10/10Topics1 topics
0/10Wiki
Inputs used
topicshacktoberfest
has_wikino
homepagehttps://www.doctrine-project.org/projects/annotations.html
docs_sitehttps://www.doctrine-project.org/projects/annotations.html
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

40Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0.2/2.5CI-Tests2 out of 17 merged PRs checked by a CI test -- score normalized to 1
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-ReviewFound 12/19 approved changesets -- score normalized to 6
2.5/2.5Contributorsproject has 76 contributing companies or organizations
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesno data
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not 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_aggregate4
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.

39Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
34.7/40Legible commit history65 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.65
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
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
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
toolchain_manifests
dependency_bot_commit_share0
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.6/55Manageable file sizes1/140 source files over 60KB
Inputs used
primary_languagePHP
largest_source_bytes66,857
source_files_sampled140
oversized_source_files1

Key facts

6,731GitHub stars
100contributors
4commits, last 12 months
259days since last push
38releases
5bus factor
26open issues
Packagistpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 233 ⇿
0Stars
233Forks
38Releases

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.

0408012016020024022652013-022019-112026-07
Major 1Minor 13Patch 24

Each point covers 13 days.

OpenSSF Scorecard 4.0 / 10
4.0aggregate

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:20 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
1CI-Tests2 out of 17 merged PRs checked by a CI test -- score normalized to 1
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 12/19 approved changesets -- score normalized to 6
10Contributorsproject has 76 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 2
RegistryPackageVersion constraintManifest
Packagistdoctrine/lexer^2 || ^3composer.json
Packagistpsr/cache^1 || ^2 || ^3composer.json
All dependencies 10

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

RegistryPackageVersionRelation
Packagistdoctrine/lexerdirect
Packagistpsr/cachedirect
Packagistdoctrine/coding-standardindirect
Packagistdoctrine/docs-builderindirect
Packagistext-tokenizerindirect
Packagistphpindirect
Packagistphpstan/phpstanindirect
Packagistphpunit/phpunitindirect
Packagistsymfony/cacheindirect
Packagistvimeo/psalmindirect
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.