spryker/search
Healthy and suitable to depend on. It has a long release history, a current stable release, recent activity from five contributors, tests, documentation, and organizational backing. The repository lacks a security policy and explicit workflow token permissions, which are transparency gaps but not adoption blockers.
88%
Total Score
100
100
94
75
Health Score Breakdown
Composer build tooling is present, but no security scanning tools were detected. The missing scanning coverage is a modest repository hygiene concern, not evidence of abandonment.
No SECURITY.md or other security policy was found, leaving vulnerability reporting and response expectations undocumented.
The only workflow lacks top-level token permissions. Although no write permission was explicitly requested, the absence of a restrictive declaration is a workflow-hardening gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spryker/gui Version ^3.0.0 || ^4.0.0 || ^5.0.0 | — | — |
spryker/log Version ^3.0.0 | — | — |
spryker/twig Version ^3.0.0 | — | — |
spryker/money Version ^2.0.0 | — | — |
spryker/store Version ^1.19.0 | — | — |
Weekly Downloads
Info
- Last Published
- 8 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.