Example project
35%
Total Score
unhealthy
Risky: no releases or repository updates since June 2019, with no README and no clear package-to-repository match.
The package has had no release in more than 7 years, with all four releases concentrated on June 28, 2019 and none in the last 12 months. That is strong evidence of abandonment risk.
The repository is not marked archived, but it was last pushed more than 7 years ago, which reinforces the release-history evidence that active maintenance has stopped.
The package contains only four files—two source files, composer.json, and .gitignore—with no documentation or test material. This minimal tree is consistent with an example, but provides little evidence of maturity.
The artifact has no README, while tests and a changelog are normally expected in the source repository rather than a published Composer package. For a small example-style library, the missing consumer documentation still reduces transparency.
The linked repository name does not match the package name, and no README mention was collected. That weakens confidence that the repository is the package's dedicated upstream source.
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.