The package is small and focused, with a clear README, MIT licensing, repository tests, and no install-time scripts. Its young release history and no commits in the last three months leave long-term maintenance capacity unproven.
62%
Total Score
50
100
83
75
The package is young at about five months old and has 11 releases, but those releases are clustered over roughly two weeks with a median interval of about 39 minutes, so long-term cadence is not yet established.
The repository has had zero commits and zero active maintainers in the last three months. For a package this young, that makes ongoing maintenance capacity uncertain even though the latest release is recent in the observed history.
The repository has no stars, forks, or watchers. Popularity is only supporting evidence, but the absence of any adoption signal provides no external confidence to offset the limited maintenance history.
Composer build tooling is present, but no security-scanning tooling was detected, leaving an avoidable transparency and defensive-maintenance gap.
The repository has no security policy. This is a modest transparency gap for consumers who need a clear vulnerability-reporting path, not evidence that the package is unsafe.
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.