The MIT license, tests, tiny dependency surface, and matching repository improve transparency. Missing security scanning and a very small public footprint leave maintenance resilience limited.
56%
Total Score
50
100
75
83
The package has only two releases, and none in the last 12 months; its latest release was nearly two years ago. This indicates limited ongoing maintenance, though the short 18-day interval between the initial releases suggests a coherent launch cycle.
There were zero commits and zero active maintainers in the last three months. Combined with the last push being nearly two years ago, this is meaningful evidence of inactivity.
The repository has zero stars and forks and only one watcher. Popularity is not required for health, but this provides little evidence of a broad user or contributor community.
Composer is used for the build, which fits the package ecosystem, but no security scanning tools are configured. The missing scanning reduces security-process transparency without proving the package is unsafe.
The linked repository is not archived, so the project remains technically open to maintenance. Its last push was nearly two years ago, however, which aligns with the stale release history.
We didn't find any vulnerabilities for this package.
No maintainer information available.
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.