cr0w/phrazor

The package includes clear documentation, tests, an MIT declaration, and only two runtime requirements. Its organization-backed repository is linked correctly and not archived, but limited security tooling leaves less evidence for long-term maintenance.

Latest v0.1.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the only release, published 190 days ago, so the project has limited history and no demonstrated release cadence. Its age is enough to provide some evidence, but not enough to establish sustained maintenance.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last 3 months, reducing evidence that issues and fixes are being actively handled. The project is still relatively young, so this is a maintenance caution rather than proof of abandonment.

Repo tooling

Composer is used for the build, which fits the package, but no security scanning tools are configured. That weakens repository hygiene and supply-chain transparency.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it does not by itself make the release unfit.