The small codebase has tests, a README, no runtime dependencies, and an MIT declaration. A single release, one registry maintainer, and no security scanning leave limited evidence of long-term support.
65%
Total Score
67
100
75
88
Only one registry maintainer is listed, which limits visible publishing redundancy. Organization backing provides some context, but it does not demonstrate active maintenance by itself.
The package has made only one release, with no subsequent release activity over about 11 months. That leaves maintenance continuity unproven for a dependency.
There are no open issues or pull requests and no activity in the last month. For a small package this is not decisive, but it supplies little evidence of an active user or contributor community.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these counts provide no external adoption signal to offset the thin release history.
Composer build tooling is present, but no security-scanning tool was detected. 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.