Testing and packaging are solid, with a matching repository and MIT licensing. The last registry release was more than three years ago, while recent repository activity is absent and workflow references are unpinned.
62%
Total Score
75
88
50
There have been no releases in the last 12 months, and version 2.0.0 was published more than three years ago. This materially raises maintenance and abandonment concerns.
The repository recorded no commits and no active maintainers in the last three months. This reinforces the concern raised by the long release gap, although the January 2025 push shows it is not archived.
The project uses Composer and Make, but no security scanning tools were detected. That is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
The workflow audit completed without reported findings or dangerous triggers, but all three action references are unpinned. This leaves avoidable build reproducibility and third-party change risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spryker/log Version ^1.0.0 || ^2.0.0 || ^3.0.0 | — | — |
spryker/quote Version ^2.0.0 | — | — |
spryker/checkout Version ^6.0.0 | — | — |
spryker/permission Version ^1.0.0 | — | — |
fond-of-oryx/splittable-quote Version ^1.0.0 || ^2.0.0 | — | — |
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.