This release appears suitable for dependency use: it has a stable 2.2.12 version, 46 releases over roughly 3.6 years, seven releases in the last 12 months, a recent repository push, and clear organization ownership with the repository matching the package. The main concerns are the absence of tests and a changelog, limited recent commit activity concentrated entirely in one contributor, and no security scanning or security policy; these reduce confidence in maintenance depth and transparency but do not indicate abandonment or registry unfitness.
78%
Total Score
70
100
89
90
Only one registry account has publish access. This is not decisive because the repository is owned by an organization, but it still leaves registry publishing dependent on a narrow account base.
A README is present and the repository uses GitHub Releases, but both the artifact and repository lack tests and a changelog. For a reusable utility library, the missing test coverage is a genuine maintenance and verification gap.
One contributor made all 2 commits in the last 3 months, producing a 100% top-contributor share. Organizational ownership partially mitigates handoff risk, but the observed recent activity remains concentrated.
The repository recorded 2 commits in the last 3 months, showing recent activity, but the volume is low for a reusable utility library and limits evidence of active maintenance depth.
Composer build tooling is present, but no security scanning tools are configured. The build setup is healthy, while the missing scanning coverage is a transparency and supply-chain hygiene gap.
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.