Usable with caveats: the package is clearly licensed, matches its organization-owned repository, and has a stable release, but it has had no commits in the last three months and only two releases concentrated on one day. Its zero-star, zero-fork repository and lack of security policy also indicate a small, lightly maintained project.
55%
Total Score
75
100
78
83
There have been only two releases, both within about 1 hour, and no later release is shown during the package's roughly 227-day lifetime. This gives limited evidence of sustained release maintenance.
The repository recorded 0 commits and 0 active maintainers in the last three months. For a library, this is a meaningful maintenance and abandonment concern, even though the project is relatively new.
The repository has 0 stars, 0 forks, and 0 watchers. Popularity is only supporting evidence, but these values provide no community-maintenance buffer alongside the inactive commit history.
Composer build tooling is present, but no security scanning tooling is configured. This is a transparency and maintenance-hygiene gap rather than evidence that the package is unsafe.
The linked repository is not archived, although its last push was about 7 months ago, consistent with the separate evidence of stalled recent activity.
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.