The release has a clear README, tests, and a repository that matches the package; it also avoids install-time scripts. Its 16 runtime dependencies add maintenance complexity, while the lack of security scanning limits transparency.
38%
Total Score
50
50
81
83
Only two releases were published, with the latest more than 10 years ago and none in the last 12 months. This is strong evidence of abandonment risk for a library dependency.
The repository recorded no commits and no active maintainers in the last 3 months, consistent with the long release gap and indicating no current maintenance capacity.
Sixteen runtime dependencies create a relatively broad maintenance and compatibility surface for a small validation library. The signal does not show those dependencies are unsafe, so this is a caution rather than a severe risk.
Composer build tooling is present, but no security scanning tools were detected. That limits repository transparency and automated hygiene evidence, although it is not evidence of malicious behavior.
The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a transparency gap, though the package's age and inactivity are more consequential.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
doctrine/orm Version * | — | — |
nesbot/carbon Version ^1.21 | — | — |
fzaninotto/faker Version ~1.5.0 | — | — |
symfony/serializer Version ^2.7 | — | — |
zendframework/zend-http Version ^2.5 | — | — |
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.