Test Case
38%
Total Score
unhealthy
Risky: no releases since 2022, an unrelated-looking repository, and no declared or detected license.
Only two releases were published, both in January 2022, with no release in more than four years. This is strong evidence of abandonment risk for a dependency.
No license is declared, detected, or included in the package or linked repository. Without licensing terms, relying on the code creates legal uncertainty.
The artifact and repository each contain only four files, including a single PHP entry point and a short README. This minimal footprint may be intentional, but provides little evidence of mature project structure.
The linked repository is named “learngit” rather than the package name and does not mention the package in its README. That weakens confidence that the repository is the package’s actual project home.
The linked repository has no security policy. For a small package this is not decisive, but it reduces transparency around vulnerability reporting.
We didn't find any vulnerabilities for this package.
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.