Tests, documentation, licensing, and a small dependency footprint support straightforward use. There is no security policy or security scanning, increasing the work needed for sensitive deployments.
52%
Total Score
0
100
64
75
The package has had no release in nearly six years: its latest release was in November 2020, with zero releases in the last 12 months. This is strong evidence of abandonment risk despite the eight-release history.
There were zero commits and zero active maintainers during the last three months. Combined with the old last push, this indicates little current capacity to fix defects or respond to changes.
The repository has four stars, one fork, and one watcher, indicating a small user and contributor base. Popularity is only supporting evidence, but this offers little external maintenance capacity to offset the stale activity.
Composer is used for builds, which fits the package ecosystem, but no security scanning tools are configured. The missing scanning is a modest transparency and maintenance gap rather than evidence of a defect.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This matters for a library that may be embedded in applications.
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.