Usable with caveats: the package is well-documented, tested, licensed, and backed by an active organization, but it is young and shows no commits in the last three months. The single registry maintainer and missing security policy add modest continuity and transparency concerns.
68%
Total Score
75
100
78
80
Only one registry account has publishing access, which creates a continuity risk if that account becomes inactive. The organization-owned repository provides some compensating project backing.
The package is only 238 days old and has three releases, with a median interval of about 119 days. That is limited history for judging long-term maintenance, though a release was published recently.
The repository recorded zero commits and zero active maintainers during the last three months. This is a meaningful maintenance concern, despite the recent release and repository push timestamp.
The repository has one star and no forks or watchers. This indicates limited external adoption or review, but popularity alone is supporting evidence rather than a health verdict.
Composer build tooling is present, but no security-scanning tool was detected. The missing scanner is a modest transparency 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.