The package is clearly identified, licensed, documented, and backed by an organization with a matching repository. Maintenance evidence is thin after its only release, while all four workflow actions are unpinned and no security policy is present.
62%
Total Score
75
88
75
This is the only release, published 485 days ago, with no releases in the last 12 months. That leaves little evidence of an ongoing release cadence.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the single-release history, this is meaningful evidence of limited current maintenance.
Composer build tooling is present, but no security-scanning tooling was detected. That is a hygiene gap, not evidence that the package is unsafe by itself.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.
The workflow audit completed fully and found no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, all four action references are unpinned, so their inputs are not fixed to immutable revisions.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/log Version ^3.0.0 | — | — |
spryker/store Version ^1.16.1 | — | — |
spryker/config Version ^3.6.0 | — | — |
spryker/kernel Version ^3.75.0 | — | — |
spryker/propel-orm Version ^1.17.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.