The small six-file codebase is easy to inspect, with a README, release notes, MIT licensing, and no install-time scripts. Its maintenance record is thin, with only one release and no commits in the last three months, while the repository has no security policy or scanning.
62%
Total Score
50
100
88
88
The repository is owned by an individual account rather than an organization, so there is no organizational backing signal to offset the single-maintainer publishing context. The linked repository does match the package and references it, which supports ownership transparency.
The package has only one release, published about 11 months ago, so there is little release history to demonstrate sustained maintenance. No other provided signal establishes an active development cadence.
There were zero commits and zero active maintainers in the last three months. For a package with only one release, that leaves limited evidence of ongoing maintenance capacity.
Composer build tooling is present, but no security-scanning tooling was detected. The missing scanner is a modest repository-hygiene gap rather than evidence that the release is unsafe by itself.
The repository has no security policy. For a small package this is a transparency and reporting gap, although the matching repository, license, and visible source provide some compensating context.
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.