crazymus/pvalidate

The package has a usable README, repository tests, a stable release, and no install-time scripts. The declared MIT license conflicts with the detected Apache-2.0 license, while 11 issues remain open and security scanning is absent.

Latest v2.0

Packagist

40%

Total Score

Maintainer Stability

Maturity

Supply Chain

100

Health Score Breakdown

Release history

The latest release was about seven years ago, and there have been no releases in the last 12 months. Four releases over a short initial period show some history, but the prolonged pause raises abandonment risk.

Repo commit activity

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

License

A license file is present, but the manifest declares MIT while the artifact license file is detected as Apache-2.0. This mismatch creates avoidable uncertainty about the terms governing the release.

Repo issue activity

Eleven issues remain open, with no new or closed issues and no pull-request activity in the last month. This supports the broader indication that the project is not being actively tended.

Repo tooling

Composer is used for the build, but the repository reports no security-scanning tools. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.