The package is internally consistent, has a matching repository, and installs without lifecycle scripts. Its documentation and tooling are limited, leaving maintainers with little evidence to support long-term adoption.
40%
Total Score
0
67
50
There has been only one release, published more than 12 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk.
There were no commits or active maintainers in the last three months, consistent with the package's long period without releases and increasing abandonment risk.
No license declaration, license file, or detected repository license was found. That creates a material legal and adoption concern for a dependency.
Composer is used for the build, but no security scanning tools were detected. This is a meaningful security-hygiene gap for an old package, though it does not by itself establish unsafe behavior.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This compounds the maintenance concerns of an otherwise inactive project.
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.