The release is well documented, licensed, tested, and backed by a repository that matches the package. Its prerelease status and missing security scanning add some uncertainty for long-term adoption.
56%
Total Score
0
71
75
The package has existed since 2015 with seven releases, but it has had no release in about seven years and none in the last 12 months. That is strong evidence of abandonment risk despite its established history.
There were no commits and no active maintainers in the last three months. Combined with the old last push, this materially raises the risk that defects and compatibility issues will remain unresolved.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and hygiene gap, not evidence that the package is unsafe.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This matters more for a dependency intended to process editor or database content.
This release is a prerelease beta, and recent releases include a meaningful prerelease share. That reduces confidence in stability for a dependency, although the package has a stable major version history.
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.