The project has had no commits or releases in the last three months, despite a burst of 14 releases on one day. It remains small and well-scaffolded, with tests, release notes, an active repository, and organizational ownership, but lacks a security policy and pins none of its workflow actions.
68%
Total Score
75
100
83
75
The package has 14 releases, but all arrived on one day and there were no releases in the last 12 months. This suggests limited demonstrated release continuity, though it is not abandonment by itself.
There were zero commits and zero active maintainers in the last three months. The recent repository push shows the project is not abandoned, but current development activity is still thin.
The repository has 3 stars and no forks, indicating a small user and contributor base. Popularity is supporting evidence only, so this modestly limits confidence rather than deciding the verdict.
The project uses Make and Composer, but no security scanning tools were detected. This is a hygiene gap, not a severe dependency risk on its own.
The repository has no security policy. That reduces disclosure transparency, although it does not by itself show poor maintenance or unsafe code.
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.