Clear documentation, tests, and a lightweight dependency set support adoption. Organization backing and recent releases help, but the project is only 44 days old and has no security policy.
62%
Total Score
83
100
81
50
Six releases arrived within 44 days, showing active early development, but the median interval is about 16 minutes, indicating a very new and bursty release history rather than established cadence.
All eight recent commits came from one contributor, creating a meaningful continuity risk. Organization ownership provides some backing, but no second active contributor is shown.
Composer build tooling is present, but no security scanning tools were detected. For a package distributing security patches, that is a transparency and assurance gap.
The repository has no security policy, leaving no documented path for reporting vulnerabilities or handling security issues.
The assessed 1.0.0 release is not consistent with the reported latest version 0.1.4, and the project is not established as a stable major line. This suggests versioning or registry-state uncertainty.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.