spryker/product-group
The repository remains active with five maintainers and six commits in three months, and the package includes tests, a changelog, release notes, and a license. Missing security policy and explicit workflow permissions are modest transparency gaps.
82%
Total Score
100
100
88
80
Health Score Breakdown
The package has existed since 2017 with nine releases, but it has had no registry release in the last 12 months; the latest release was about 13 months ago. This indicates a slower cadence but not abandonment because the repository remains active.
The repository uses Composer build tooling, but no security-scanning tools were detected. Build support is present; the missing scanning layer is a modest process gap.
No repository security policy was found. This reduces transparency about vulnerability reporting, though it is not evidence that the package is unsafe or unmaintained.
The only workflow lacks a top-level permissions declaration, so its token permissions are less explicit than preferred. No top-level write permissions were detected.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spryker/twig Version ^3.0.0 | — | — |
spryker/touch Version ^3.0.0 || ^4.0.0 | — | — |
spryker/kernel Version ^3.52.0 | — | — |
spryker/product Version ^5.0.0 || ^6.0.0 | — | — |
spryker/storage Version ^3.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year 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.