techdivision/persistencecontainer

Registry deprecationdanger

Packagist marks the entire package as abandoned and names appserver-io/appserver as its replacement. This is a severe adoption risk because new maintenance is directed elsewhere.

Release historydanger

The package has had no releases in over 11 years, despite 25 releases during its earlier active period. That long release gap strongly indicates abandonment for a dependency intended for ongoing use.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, with its last push over 11 years ago. This provides no evidence of current maintenance capacity.

Repo package mentioncaution

The linked repository neither matches the package name exactly nor mentions the package in its README, creating some uncertainty about package-to-repository alignment. The repository name is nevertheless closely related, so this is a secondary concern.

Security policycaution

The repository has no security policy. This is a transparency gap, but it is secondary to the package's explicit abandonment and long period without releases.