Its README is clear and the repository matches the package, making its intended use easy to verify. The small project has no security policy or automated security scanning, so future compatibility work is unlikely to be covered.
42%
Total Score
0
71
75
The package has had only one release, published about seven years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency that may need compatibility updates.
There were no commits and no active maintainers in the last three months, consistent with a project whose last repository activity was about seven years ago. This materially increases maintenance and abandonment risk.
The project uses Composer for builds, which is appropriate, but no security scanning tools were detected. That leaves an avoidable gap in ongoing dependency and release hygiene.
The repository has no security policy. For a package that integrates into an application framework, this reduces transparency about how security issues would be reported and handled.
Version 0.0.1 remains an early, non-stable-major release, and the package has no later version to demonstrate maturation. Its non-prerelease status provides little compensation for the lack of evolution.
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.