spryker/container
Healthy and suitable to depend on. It has frequent recent releases, active multi-contributor maintenance, tests, documentation, and an unarchived organizational repository; the main caveats are the missing security policy and undeclared workflow token permissions.
88%
Total Score
88
94
80
Health Score Breakdown
There were no new or closed issues or pull requests in the last month, and one pull request remains open. This is a minor activity gap, but it is outweighed by recent commits and frequent releases.
The repository uses Composer for builds, but no security-scanning tool was detected. Build support is present, while the lack of visible security automation is a modest transparency gap.
The repository has no security policy. This makes vulnerability reporting and response expectations less transparent, although it does not by itself indicate abandonment.
The only workflow lacks top-level token permissions, and no read-only permissions are declared. This is a workflow-hardening gap, though no write permissions or dangerous workflow patterns were observed.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 psr/container Version ^1.0.0 | — | — |
spryker/kernel Version ^3.48.0 | — | — |
spryker/symfony Version ^3.0.0 | — | — |
spryker/transfer Version ^3.42.0 | — | — |
spryker/module-finder Version ^1.4.0 | — | — |
Weekly Downloads
Info
- Last Published
- 6 days ago
- Created
- 7 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.