My first Composer project
38%
Total Score
unhealthy
Risky: no releases or commits for about seven years, with a repository that does not identify this package.
The latest release was about seven years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk for a package receiving a new dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and providing no evidence of current maintenance.
The linked repository is named composer-test rather than this package and its README does not mention bstorck/hello-world. That raises concern that the source repository may not clearly belong to the published package.
The repository uses Composer build tooling, but no security-scanning tools were detected. For this small package that is a modest transparency gap, not a severe risk by itself.
The linked repository is not archived, although its last push was about seven years ago. The active archive status does not compensate for the observed inactivity.
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.