The license metadata conflicts with the Apache-2.0 license file, and the repository has no security policy or scanning tools. The package is a documented skeleton with a stable version and no deprecation, but its maintenance evidence is weak.
42%
Total Score
50
71
50
This is the package's only release, published about three years and eight months ago, with no releases in the last 12 months. That leaves little evidence of ongoing maintenance for a dependency.
The manifest declares AGPL-3.0-or-later, while the detected LICENSE file says Apache-2.0. Although a license file exists, the mismatch creates legal uncertainty for adopters.
The package uses a post-create-project-cmd lifecycle script, adding install-time behavior that consumers should understand. The signal does not show that the script is harmful, so this is a limited caution.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long-stalled release history. The repository is not archived, but it shows no recent maintenance activity.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
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.