Tests, licensing, and repository alignment provide a solid baseline for adoption. Maintenance appears slow, with no release in about 20 months and no commits in the last three months; workflow references are also unpinned.
62%
Total Score
75
83
75
Only two releases exist, with no release in the last 12 months and a median interval of about 20 months. This indicates a slow maintenance cadence, though it may be adequate for a stable integration module.
The repository had no commits and no active maintainers in the last three months, which is evidence of currently limited maintenance activity.
The project uses Make and Composer, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than a severe risk.
No security policy was found in the repository, reducing clarity about vulnerability reporting and response practices.
The single workflow was fully analyzed with no dangerous triggers or audit findings, but all three action references are unpinned, leaving dependency versions exposed to unexpected changes.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.5 | — | — |
spryker/glue-application Version ^1.0.0 | — | — |
spryker/glue-application-extension Version ^1.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.