The repository remains available and received a release within the last year, but its README tells users to treat the package as deprecated. No commits were recorded in the last three months, and the repository has no security policy, making continued support uncertain.
43%
Total Score
50
71
50
The published README explicitly states that this package should be considered deprecated, which is a direct warning against taking a new dependency despite the README being present.
The repository recorded zero commits and zero active maintainers in the last three months. That inactivity reinforces the package's own deprecation warning and raises support risk.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap for a package intended as a dependency.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities.
Version v0.9.2 is not a stable major release, although it is not marked as a prerelease. This adds some maturity uncertainty but is secondary to the package's explicit deprecation notice.
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.