The package includes tests, a GitHub release, and no install-time scripts. Its single-release history and fully unpinned CI actions leave maintenance and build reproducibility concerns for a dependency.
52%
Total Score
100
67
67
Only one release exists, published about 20 months ago, with no releases in the last 12 months. This leaves the project's ongoing maintenance uncertain despite the repository remaining unarchived.
The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these values provide little evidence of community validation alongside the single-release history.
Composer build tooling is present, but no security scanning tool was detected. This is a modest transparency and maintenance gap, not a severe dependency risk by itself.
The repository has no security policy. For a small package this is a hygiene gap, but it does not independently indicate that the release is unsafe to depend on.
Version 0.0.1 is not a stable major release, so its API may change substantially if development resumes. The absence of prerelease labeling does not compensate for the very early version.
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.