The package includes a README, release notes, a matching repository, and an MIT declaration. Its last release and repository push were over seven years ago, with no recent commits and only one maintainer, making dependency risk substantial.
40%
Total Score
25
78
83
The package has had no release in over seven years: all six releases were published on the same day in May 2019, and there were no releases in the last 12 months. This strongly suggests abandonment despite the package not being deprecated.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since 2019. This is a substantial maintenance and abandonment concern.
One registry maintainer provides a narrow publishing base, which increases continuity risk when the project also shows no recent release or commit activity. The repository is user-owned rather than organization-backed, so there is no provided evidence of broader maintenance capacity.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these values provide no community signal to offset the lack of maintenance activity.
Composer is used for the build, which fits the package, but no security-scanning tools are present. For a small package this is a modest hygiene gap rather than a standalone reason to reject it.
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.