Healthy and suitable to depend on. It has a long, active release history, broad recent contributor activity, complete package and repository documentation, and no deprecation or archival concerns; security-policy and workflow-permission gaps are the main caveats.
88%
Total Score
88
89
80
There were no new or closed issues or pull requests in the last month, and one pull request is open; this is a limited activity signal but does not outweigh the recent commits and releases.
The repository has zero stars and only two forks, which offers little community validation; this is supporting evidence only and is outweighed by the package's active releases and organizational backing.
Composer build tooling is present, but no security-scanning tool was detected; the missing scanning layer is a transparency gap rather than evidence of abandonment.
The repository has no security policy, leaving vulnerability-reporting expectations and response procedures undocumented.
The only workflow does not declare top-level token permissions. No write permissions were observed, but explicit least-privilege settings would provide stronger workflow hygiene.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/url Version ^3.3.0 | — | — |
spryker/store Version ^1.7.0 | — | — |
spryker/kernel Version ^3.77.0 | — | — |
spryker/locale Version ^3.1.0 || ^4.0.0 | — | — |
spryker/laminas 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.