leoshtika/pagination

Release historydanger

The latest release was about 10 years ago, with no releases in the last 12 months and only three releases overall. This is strong evidence of abandonment risk, although the package is stable rather than prerelease.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the last push being about 10 years ago. This materially increases abandonment and compatibility risk.

Dependency profilecaution

The package has two runtime dependencies, leoshtika/database and leoshtika/logger. This is a modest dependency surface, though each dependency adds maintenance exposure to an already old project.

Maintainerscaution

One registry maintainer is consistent with an individual-owned project, so it is not inherently a problem. Combined with no recent commit activity, it leaves little visible maintainer redundancy.

Project backingcaution

The repository is owned by the same individual namespace as the package, providing clear ownership, but it is user-backed rather than organization-backed and has only one registry maintainer.