spryker/content-file-gui
Healthy and suitable to depend on, with an established release history and active organization-backed maintenance. The main caveats are the missing security policy and limited workflow permission hardening, while repository popularity is minimal.
86%
Total Score
100
100
94
80
Health Score Breakdown
Composer build tooling is present, but no security scanning tools were detected. This is a transparency and assurance gap, though it is not evidence of abandonment.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.
The single workflow declares no top-level token permissions, so its GitHub Actions access is less explicitly constrained than recommended; no write permissions were observed.
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.45.0 || ^4.0.0 || ^5.6.0 | — | — |
spryker/kernel Version ^3.33.0 | — | — |
spryker/locale Version ^3.2.0 || ^4.0.0 | — | — |
spryker/symfony Version ^3.2.2 | — | — |
spryker/transfer Version ^3.25.0 | — | — |
Weekly Downloads
Info
- Last Published
- 5 days ago
- Created
- 7 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.