spryker/api-key-gui
The repository has no published security policy, and two of four workflow actions are unpinned. A release note, changelog, license file, and seven active contributors provide useful transparency and continuity.
86%
Total Score
100
100
94
75
Health Score Breakdown
The repository uses Composer build tooling, but no security-scanning tools were detected. This is a modest process gap, though current commits and releases provide compensating maintenance evidence.
No security policy was found in the repository. That weakens the project's published process for reporting and handling vulnerabilities, although it does not by itself indicate abandonment.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings; however, two of four action references are unpinned. The missing top-level permissions block is acceptable on its own, while the unpinned references are a minor reproducibility and supply-chain hygiene 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.38.0 || ^4.0.0 || ^5.8.0 | — | — |
spryker/user Version ^3.0.0 | — | — |
spryker/kernel Version ^3.33.0 | — | — |
spryker/api-key Version ^2.0.0 | — | — |
spryker/symfony Version ^3.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 23 hours ago
- Created
- 3 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.