Belajar Membuat library di composer
38%
Total Score
unhealthy
Risky: no releases or commits for about four years, minimal documentation, and a repository that does not match the package name.
This package has only one release, published about four years ago, with no releases in the last 12 months. That strongly limits evidence of ongoing maintenance.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and increasing abandonment risk.
The artifact has no README, tests, or changelog, but the release notes document this exact version and tests and changelogs are normally kept in the source repository rather than published artifacts. The missing README still weakens consumer guidance for a library.
The linked repository name does not match the package name, and no README package mention was available. This makes package-to-source ownership less transparent, although it could still be a small learning project.
Composer is used as the build tool, but no security scanning tools were detected. The absence of scanning is a modest hygiene concern, not evidence of maliciousness.
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.