The project has a long release history, a clear README, repository tests, and a recent release. Its single registry maintainer and lack of security scanning add modest maintenance risk.
70%
Total Score
50
100
94
50
The repository is owned by an individual user rather than an organization. This does not indicate poor health, but it provides less visible institutional backing for long-term continuity.
The repository recorded zero commits and zero active maintainers in the last three months. The recent release limits the abandonment concern, but the current absence of development activity still lowers confidence in ongoing maintenance.
There were no new or closed issues or pull requests in the last month, with 10 open issues and four open pull requests. This is a modest sign of limited current project interaction, though the recent release is compensating evidence.
Composer build tooling is present, but no security scanning tool was detected. The missing scanning is a hygiene gap rather than evidence that the release is unsafe.
The repository has no security policy. This reduces transparency about vulnerability reporting and response expectations, especially for a library used in application input handling.
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.