pragmarx/recovery

The repository remains intact, documented, and tested, with a small dependency surface and no install-time scripts. Its lack of recent release or commit activity and absent security policy make long-term support uncertain; pin this version if adopting.

Latest v0.2.1

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only 3 releases since September 2017, with no release in about 5 years and no releases in the last 12 months, indicating weak ongoing maintenance.

Repo commit activity

There have been no commits and no active maintainers in the last 3 months, consistent with the long gap since the latest release and raising abandonment concerns.

Project backing

The repository is owned by an individual rather than an organization, so the single registry maintainer provides only limited visible backing for continued maintenance.

Repo issue activity

Two issues and one pull request remain open, with no issues or pull requests closed in the last month, suggesting limited recent project responsiveness.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected, reducing automated security coverage for a package that handles recovery-code generation.