doctrine/annotations

Registry deprecationdanger

Packagist marks the entire package as abandoned, with no replacement specified. This is a severe adoption and maintenance-risk signal for a new dependency.

Release historycaution

The package has a long release history with 43 releases, but its latest release was about two years ago and there were no releases in the last 12 months. That supports the documented transition to a feature-complete, bugfix-only project but reduces confidence in ongoing maintenance.

Repo commit activitycaution

There were no commits and no active maintainers during the last three months. This is consistent with a feature-complete project but still leaves little evidence of current maintenance capacity.

Security policycaution

The repository has no security policy. This is a transparency gap, although the project's static-analysis tooling and feature-complete scope provide some compensating evidence.

Token permissionscaution

None of the six workflows declares top-level token permissions, leaving workflow access less explicit than recommended. No workflow declares top-level write access, limiting the severity of this concern.