spryker/manual-order-entry
Healthy and suitable to depend on. It has a recent release, active organization-backed development, balanced contributors, tests, and clear package structure; the main caveats are limited repository security documentation and undeclared workflow token permissions.
88%
Total Score
100
100
94
80
Health Score Breakdown
Composer build tooling is present, but no security-scanning tool was detected. The missing scanner is a transparency and defense-in-depth gap, though other repository hygiene is good.
The repository has no security policy. This weakens the documented process for reporting and handling vulnerabilities, although it does not by itself indicate abandonment.
The repository's CI workflow does not declare top-level token permissions. No workflow requests top-level write access, but explicitly limiting permissions would provide stronger CI hygiene.
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 | — | — |
spryker/symfony Version ^3.1.0 | — | — |
spryker/sales-extension Version ^1.14.0 | — | — |
Weekly Downloads
Info
- Last Published
- 7 days ago
- Created
- 8 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.