Clear licensing, release notes, and a substantial artifact improve confidence. Only one commit from one contributor in the last three months, no security policy, and a repository mismatch leave meaningful maintenance and ownership concerns.
67%
Total Score
70
88
83
All recent commits came from a single contributor, creating a concentrated maintenance path. Organizational backing provides some handoff capacity but does not remove the current concentration.
Only one commit was made in the last three months by one active maintainer. This shows recent maintenance but a very thin current activity level.
The repository has one open issue and one open pull request, with no issues or pull requests opened or merged in the last month. This is limited evidence of active community maintenance.
The repository name does not match the package name and its README does not mention this package. Although naming differences can occur, both indicators together raise concern that the linked source may not clearly identify the published package.
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning coverage is a modest transparency and maintenance concern.
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.