Clear documentation, tests, release notes, and balanced contributor activity support adoption. The proprietary license and absence of repository security scanning warrant checking compatibility and controls.
82%
Total Score
100
88
50
The release declares a proprietary license and includes a LICENSE file, so it is licensed rather than undocumented. However, proprietary terms may restrict use or redistribution and should be checked for project compatibility.
Composer build tooling is present, but no security-scanning tool was detected. The missing scanning process is a modest transparency concern, not evidence of unsafe code by itself.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This is a process gap, though the active organization-backed project partly reduces abandonment concern.
The single workflow was fully analyzed with no reported audit findings, no untrusted checkouts, and no script injection. Two of four action references are unpinned, which is a minor reproducibility concern; the workflow has no top-level permissions block and no broad write permissions.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/tax Version ^5.11.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/storage Version ^3.0.0 | — | — |
spryker/transfer Version ^3.27.0 | — | — |
spryker/event-behavior Version ^1.0.0 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.