spryker/transfer
Healthy and suitable to depend on. It has a long release history, a recent release, active contributors, comprehensive tests and documentation, and clear organizational backing; the main gaps are the absent security policy and limited workflow permission hardening.
88%
Total Score
100
100
94
80
Health Score Breakdown
Composer build tooling is present, but no security-scanning tool was detected. The missing scanning layer is a transparency and maintenance gap, though it is partly offset by the repository's tests and controlled workflow profile.
The repository has no security policy. That weakens vulnerability-reporting transparency for a package intended for broad application use, with no provided signal showing a compensating process.
The only workflow lacks top-level token permissions, and no workflow declares read-only permissions. Although no write permissions were detected, explicitly restricting permissions would provide stronger CI hardening.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spryker/log Version ^3.0.0 | — | — |
spryker/twig Version ^3.0.0 | — | — |
spryker/kernel Version ^3.59.0 | — | — |
spryker/propel Version ^3.21.0 | — | — |
spryker/laminas Version ^1.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 9 days ago
- Created
- 10 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.