A single maintainer and one star leave little visible backup if development stops. Strong tests, release notes, and a matching repository provide useful transparency, while unpinned workflow actions are a minor hygiene concern.
70%
Total Score
50
100
81
75
Only one registry account has publishing access. That is a limited publishing base for a user-owned project and leaves little visible redundancy if the maintainer becomes unavailable.
The package has only two releases across about 2 years and 11 months, with one release in the last 12 months. The recent release is positive, but the sparse history limits confidence in sustained maintenance.
There were no commits and no active maintainers in the last three months. Although the latest release was recent, the absence of current commit activity weakens confidence in ongoing maintenance.
The repository has one star, no forks, and one watcher. Low popularity is not decisive for a small package, but it provides little evidence of a broad support or review community.
Composer build tooling is present, but no security scanning tool was detected. This is a modest transparency and hygiene gap rather than evidence of unsafe code.
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.