Security documentation is absent, and two of four workflow actions are not pinned. Tests, release notes, a matching repository, and five recent contributors provide strong maintenance and transparency.
84%
Total Score
100
100
94
67
Composer build tooling is present, but no security-scanning tool was detected; this is a modest process gap rather than evidence of abandonment.
The repository has no security policy, leaving vulnerability-reporting expectations unclear for a package that manages uploaded and stored files.
The single workflow was fully analyzed with no injection or high-severity findings, but two of four action references are unpinned, leaving avoidable build-integrity risk.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/kernel Version ^3.30.0 | — | — |
spryker/locale Version ^3.0.0 || ^4.0.0 | — | — |
spryker/transfer Version ^3.27.0 | — | — |
spryker/propel-orm Version ^1.0.0 | — | — |
spryker/file-system Version ^2.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.