A complete README, extensive tests, MIT licensing, and a non-archived repository provide a solid baseline. The workflow is fully analyzed but uses two unpinned actions, and install/update commands deserve review before adoption.
58%
Total Score
38
100
81
50
The latest release was over five years ago, with no releases in the last 12 months, despite a history of 23 releases. This is meaningful abandonment risk for a validation library that may need current data and compatibility fixes.
The repository recorded no commits and no active maintainers in the last three months, and its last push was over four years ago. The repository is not archived, but the lack of recent activity indicates slow or absent maintenance.
The package defines post-install and post-update Composer commands. These commands add install-time behavior that consumers must understand and review, even though the signal does not establish that they are unsafe.
The registry has one publishing maintainer, and the repository owner is the same individual. This is coherent for a user-owned project, but it also indicates a thin maintainer base.
The registry namespace and repository owner match, and the repository is user-owned rather than organization-owned. This supports ownership clarity but offers no organizational backing to offset the single-maintainer risk.
We didn't find any vulnerabilities for this package.
No direct dependencies.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.