spryker/graceful-runner
Documentation, tests, and release notes make integration straightforward. The organization-backed repository has recent commits from five contributors, while the missing security policy and two unpinned workflow actions leave modest transparency and build-reproducibility gaps.
82%
Total Score
100
88
67
Health Score Breakdown
The package has only three releases since 2021, with releases typically about 2.8 years apart, which is sparse. However, one release arrived in the last 12 months and the assessed version is current, so this is a modest maintenance concern rather than abandonment evidence.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest assurance gap.
The repository has no security policy. This does not show a defect in the code, but it reduces transparency about vulnerability reporting and response.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. Two of four action references are unpinned, creating a limited reproducibility and supply-chain hygiene gap; the missing top-level permissions block is acceptable on its own.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spryker/kernel Version ^3.30.0 | — | — |
seld/signal-handler Version ^1.2.0 || ^2.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 19 hours ago
- Created
- 5 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.