The project is clearly packaged and documented, with a matching repository, MIT licensing, and tests in the source tree. Its small scope and organization backing reduce concern, but ongoing maintenance and workflow hygiene warrant attention.
67%
Total Score
67
100
88
75
The package has existed since June 2017 but has only five releases, with no release in the last 12 months and the latest release about 19 months ago. This indicates slow maintenance and lowers confidence in timely updates.
There were no commits and no active maintainers in the preceding three months. Combined with the long release gap, this is evidence of limited current maintenance capacity.
There were no new or closed issues or pull requests in the preceding month, and no pull requests are open. This is consistent with a quiet, small project but provides little evidence of active community maintenance.
Composer build tooling is present, but no security-scanning tools were detected. For a small library this is a hygiene gap rather than a severe dependency risk.
The repository has no security policy. This reduces transparency about vulnerability reporting and response, though it does not by itself show that the package is unsafe to use.
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.