The package is clearly licensed and tied to a matching organization repository. Its one-day history leaves long-term maintenance unproven, while the missing README reduces integration guidance.
60%
Total Score
75
79
75
The artifact has no README, which makes a library harder to integrate. The absence of tests and a changelog is not a packaging concern here because those normally belong in the source repository.
The package is only one day old, despite five releases in that period. This shows active initial publishing but provides no evidence of sustained maintenance yet.
No commits or active maintainers were observed in the last three months. Because the repository and package are only one day old, this is mainly an unproven-maintenance concern rather than evidence of abandonment.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency gap rather than a standalone dependency risk.
The repository has no security policy, leaving vulnerability reporting and response expectations unspecified.
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.