README, tests, licensing, and a small dependency set make integration clearer. However, no release or commit activity for about three years and no security policy or scanning reduce confidence in ongoing maintenance.
58%
Total Score
50
100
79
83
Only two releases exist, with the latest about three years ago and none in the last 12 months. This is meaningful evidence of slowing maintenance, despite the package not being deprecated.
There were no commits and no active maintainers in the last three months. Combined with the old latest release, this points to stalled maintenance rather than an actively evolving project.
Composer build tooling is present, but no security scanning tools were detected. That weakens security-maintenance transparency for a package handling password history.
The repository has no security policy. For a package dealing with password-related data, this leaves vulnerability-reporting and response expectations unclear.
Version 0.0.2 is not a stable-major release, so API stability may be less predictable. The release is not marked as a prerelease, which partly offsets that concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
laravel/framework Version ~5.1|6.*|7.*|8.*|9.* | — | — |
imanghafoori/laravel-nullable Version ^1.2 | — | — |
imanghafoori/laravel-smart-facades Version ^1.0 | — | — |
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.