Good documentation, tests, and release notes support routine adoption. The repository lacks a security policy, and two of four workflow actions are unpinned.
88%
Total Score
100
100
94
75
The repository uses Composer for its build tooling, appropriate for a Packagist package. No security-scanning tool was detected, leaving a modest process gap but not evidence of abandonment.
No repository security policy was found. This weakens vulnerability-reporting transparency, although active maintenance and release evidence partly compensate.
The single workflow was fully analyzed with no injection or high-severity findings, and it has no broad top-level write permissions. However, 2 of 4 action references are unpinned, so workflow reproducibility has a minor hygiene gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/gui Version ^4.0.0 || ^5.8.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/symfony Version ^3.0.0 | — | — |
spryker/transfer Version ^3.27.0 | — | — |
spryker/util-text Version ^1.1.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.