reva2/paxum-api

Documentation is minimal and the project has no tests or security scanning. The small, single-maintainer project is transparent about its MIT license, but its long inactivity makes future fixes uncertain.

Latest 0.2.1

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in October 2019, with no releases in the last 12 months and only three releases overall. This long release gap is a substantial maintenance concern.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the old last push, this is strong evidence of abandonment risk.

Maintainers

One registry maintainer is listed, and the repository owner is a user account rather than an organization. This leaves a thin apparent maintainer base for a project that has not been updated recently.

Project backing

The registry namespace and repository owner match, but the owner is an individual account. There is no provided evidence of organizational backing to offset the thin maintainer base.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. While this is not inherently negative, it offers no evidence of an active maintenance community.