Healthy and suitable to depend on. It has a long release history, frequent recent releases, active work from seven contributors, tests, and a matching organization-backed repository. The main caveats are the lack of a security policy and undeclared workflow token permissions.
88%
Total Score
100
100
89
80
The repository has 0 stars and 1 fork, so there is little public popularity evidence. However, popularity is only supporting evidence and is outweighed here by the package's release cadence, recent commits, and organization backing.
Composer is used as a build tool, but no security scanning tools were detected. The missing scanning evidence is a modest transparency gap, while the repository's active development and CI workflow provide some compensating project evidence.
The repository has no security policy. That weakens the project's documented process for receiving and handling vulnerability reports, although it does not indicate abandonment by itself.
The single analyzed CI workflow has no top-level token permissions declaration. This leaves workflow permissions less explicit than recommended, though no workflow was found to request top-level write access.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/gui Version ^3.45.0 || ^4.0.0 || ^5.6.0 | — | — |
spryker/event Version ^1.0.0 || ^2.3.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/locale Version ^3.0.0 || ^4.0.0 | — | — |
spryker/product Version ^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.