doctrine/annotations

Annotations Docblock Parser

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 25 minutes ago
Added to GitGenius on September 9th, 2026
Created on January 12th, 2013
Open Issues & Pull Requests: 26 (+0)
GitHub issues: Enabled
Number of forks: 234
Total Stargazers: 6,730 (+0)
Total Subscribers: 38 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Doctrine Annotations is a docblock parser that extracts and processes annotation metadata from PHP code comments.

The tool solves the problem of reading structured metadata embedded in PHP docblocks without relying on PHP's native attributes or reflection alone. It parses docblock comments to identify annotations—special markers that developers write in code documentation—and converts them into usable objects. This approach allows frameworks and libraries to attach configuration, validation rules, or other metadata directly to classes, methods, and properties in a way that is readable in the source code itself.

Developers should adopt this tool when building frameworks, libraries, or applications that need to read metadata from docblocks. It suits projects that want to support annotation-driven configuration without requiring PHP 8 attributes, or that need to maintain backward compatibility with older codebases. The tool is particularly useful for dependency injection containers, ORM systems, validation frameworks, and similar infrastructure that benefits from declarative metadata. The README does not compare this tool to alternatives, so no comparison guidance can be offered.

The project maintains a stable codebase with infrequent but deliberate updates. Pull requests receive careful review before acceptance, indicating a quality-focused approach to changes. The maintainers respond to issues and engage with the community, though the pace of activity reflects the maturity of the project rather than rapid feature development. Documentation is kept current alongside code changes, suggesting attention to usability for adopters.