a test of composer
42%
Total Score
unhealthy
A single 2020 release and five years without commits make ongoing maintenance unlikely.
There has been only one release, published in November 2020, with none in the last 12 months. This is strong evidence of abandonment risk, although the repository is not archived or deprecated.
There were zero commits and zero active maintainers in the last three months, consistent with a repository that has seen no meaningful activity for years. This materially increases abandonment risk.
The published artifact contains only LICENSE and composer.json, and the repository adds only a diagram. This very small surface may be intentional for a test package, but it offers little transparency about functionality or maintenance.
The package and repository are owned by the same individual account rather than an organization. That is not inherently unhealthy, but it provides no organizational backing to offset the inactive project.
The repository has zero stars, forks, and watchers. Popularity is not required for a healthy small package, but these counters provide no supporting evidence for project maturity alongside the inactive history.
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.