spryker/queue
Healthy and suitable to use. It has a long release history, frequent recent releases, active work from six contributors, tests and documentation, and a non-archived organization-backed repository. The main caveats are missing security scanning, no security policy, and unspecified workflow token permissions.
88%
Total Score
100
100
94
80
Health Score Breakdown
Composer build tooling is present, but no security-scanning tools were detected; this is a transparency and assurance gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.
The CI workflow does not declare top-level token permissions, so its intended GitHub token access is less explicit than recommended.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spryker/gui Version ^3.0.0 || ^4.0.0 || ^5.0.0 | — | — |
spryker/log Version ^3.0.0 | — | — |
spryker/store Version ^1.25.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/monolog Version ^2.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 9 days ago
- Created
- 9 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.