desmart/pagination

Registry deprecationdanger

Packagist marks the entire package as abandoned, with no replacement named. Package-level abandonment is a severe dependency risk even though the specific release is not separately withdrawn.

Release historydanger

The latest release was published on March 9, 2015, and there have been no releases in the last 12 months. This long release gap strongly indicates abandonment for a framework integration package.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap and abandonment status.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, with one issue still open. This adds evidence of inactivity, although the small project size limits how much issue volume alone proves.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance concern rather than a decisive risk by itself.