Organization backing, a matching repository, and an active license improve transparency. The repository includes a README and changelog, but four workflow actions are unpinned and no security policy is provided.
63%
Total Score
75
88
50
This is the package's only release, published about 16 months ago, with no releases in the last 12 months. That leaves maintenance and release continuity unproven.
There were no commits and no active maintainers in the last three months. Combined with the single-release history, this weakens confidence in ongoing maintenance.
Composer build tooling is present, but no security scanning tools were detected. This is a modest repository hygiene gap, not evidence that the release is unsafe.
The repository has no security policy, leaving vulnerability reporting and handling expectations undocumented.
The single workflow was fully analyzed without dangerous triggers or audit findings, but all four action references are unpinned. That creates a reproducibility and maintenance hygiene concern.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/url Version ^3.13.0 | — | — |
spryker/mail Version ^4.10.0 | — | — |
spryker/user Version ^3.14.1 | — | — |
spryker/store Version ^1.16.1 | — | — |
spryker/kernel Version ^3.75.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.