The small dependency surface and included tests support straightforward integration. Organization backing and a matching repository improve transparency, but the limited release history leaves less evidence of long-term support.
61%
Total Score
50
100
83
75
There were no commits and no active maintainers in the last three months, consistent with the long period since the latest release. This is the strongest maintenance concern in the available evidence.
Only two releases exist, with no releases in the last 12 months and a median interval of about 217 days. This provides limited evidence of sustained maintenance for a package now nearly two years past its latest release.
There is one open issue and no issue or pull-request activity in the last month. This adds a small transparency concern but is weaker than the lack of commits.
The repository has zero stars, forks, and watchers, so there is little visible community adoption to compensate for the inactive maintenance record. Popularity is supporting evidence rather than a verdict.
Composer is used for the build, showing basic project tooling, but no security-scanning tool was detected. The missing scanner is a hygiene gap rather than evidence of an unsafe release.
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.