The MIT license, readable documentation, and matching organization repository improve transparency. No install-time scripts or deprecation status add reassurance, while the small activity record limits confidence in long-term maintenance.
66%
Total Score
67
88
83
The package has only two releases, both within the first two days, despite being 261 days old. That limited release history makes ongoing maintenance uncertain.
One contributor made all two recent commits, creating concentrated maintenance risk. The organization-owned repository provides some capacity to hand work off, so this is a caution rather than a severe risk.
Only two commits were recorded in the last three months, indicating very light recent development activity. The recent repository push is reassuring but does not offset the sparse commit record.
Composer build tooling is present, but no security scanning tools were detected. The build setup is positive, while the missing scanning coverage is a modest process gap.
The repository has no security policy, leaving no documented path for reporting vulnerabilities. This is a transparency and maintenance gap, not 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.