A single publisher and no recent commits reduce resilience if the maintainer steps away. The package is well documented, tested, licensed, non-deprecated, and has a recent release with a matching source repository.
72%
Total Score
63
100
88
88
Only one account has registry publishing access, so publishing and continuity depend on a single individual. The matching repository and recent release provide some evidence of active ownership but do not remove the bus-factor concern.
The repository recorded zero commits and zero active maintainers in the last three months, a meaningful sign of slowed maintenance. The recent package release partially offsets this, but does not show ongoing development capacity.
There are no open issues or pull requests and no activity in the last month. This is not harmful by itself for a small stable package, but it provides little evidence of an active user or contributor community.
Composer build tooling is present, but no security scanning tool was detected, leaving a modest transparency and maintenance gap.
The repository has no security policy, so users have no documented reporting path. This is a hygiene gap rather than 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.