Its MIT license, tests, and organizational ownership improve confidence. Three unpinned workflow actions and no security policy leave avoidable build-integrity and maintenance gaps.
60%
Total Score
75
100
79
75
Repository tests are present, which is a small positive for maintainability; the missing package README is a minor consumer-documentation gap for a library extension.
Only one release exists, published about 2 years and 6 months ago, with no releases in the last 12 months. This indicates limited release maturity and raises abandonment concerns.
There were no commits and no active maintainers in the last three months. Combined with the lack of recent releases, this is meaningful evidence of limited current maintenance.
The repository uses Make and Composer build tooling, but no security-scanning tool was detected. This is a modest transparency and maintenance gap.
No repository security policy was found, leaving vulnerability-reporting expectations undocumented. This is a minor governance gap rather than evidence of unsafe code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spryker/elastica Version ^4.0.0 || ^5.0.0 || ^6.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.