The source repository is extremely small and has no security policy, limiting transparency and reviewability. Organization ownership, a stable release, and release notes provide some context, but not enough to offset the maintenance concerns.
40%
Total Score
75
79
67
No license is declared, detected, or supplied in either the package or repository. That creates a real adoption and reuse concern.
The package and repository contain only .gitignore and composer.json, leaving little implementation or documentation surface to inspect and making the project unusually opaque.
The package has only four releases and none in the last 12 months; its latest release was about 21 months ago, indicating likely stalled maintenance.
There were no commits and no active maintainers in the last three months, consistent with the roughly 21-month gap since the last release and raising abandonment risk.
Composer is used as the build tool, but no security-scanning tooling is present. This is a modest transparency and maintenance gap rather than evidence of unsafe behavior.
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.