sbooker/persistent-pointer-doctrine

Release historycaution

The package has only two releases over about five years, with roughly five and a half years between them, although one release appeared in the last 12 months. This shows recent activity but an historically sparse release cadence.

Repo bus factorcaution

All recent commits come from a single contributor, so maintenance depends heavily on one person. The repository is user-owned rather than organization-backed, providing no shown handoff capacity to offset that concentration.

Repo commit activitycaution

There was one commit from one active maintainer in the last three months, showing current activity but only limited observed maintenance capacity.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. For a small package this is a hygiene gap rather than evidence of abandonment.

Security policycaution

The repository has no security policy. This reduces transparency for reporting and handling vulnerabilities, though it is not by itself a severe dependency risk.