The package is organized, licensed, tested, and backed by an organization, with no install-time scripts. Unpinned workflow images and no security policy add supply-chain hygiene and transparency concerns.
58%
Total Score
67
100
78
75
The latest registry release was in October 2021, nearly five years ago, and there were no releases in the last 12 months. This is the strongest evidence of possible abandonment despite five total releases.
There were no commits or active maintainers in the last three months. The later repository push partly offsets this, but current development activity remains weak.
There are no open issues or pull requests and no recent issue or pull-request activity. This is consistent with a quiet project but does not independently show abandonment.
The repository has no stars and one fork, indicating limited public adoption. Popularity is only supporting evidence, so this modestly reinforces caution rather than deciding the assessment.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a moderate transparency and maintenance gap, not evidence of an unsafe package by itself.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/oms Version ^8.1.0 || ^10.0.0 || ^11.0.0 | — | — |
spryker/sales Version ^8.0.0 || ^10.0.0 || ^11.0.0 | — | — |
spryker/file-system Version ^2.0.0 | — | — |
spryker/util-encoding Version ^2.0.0 | — | — |
spryker/flysystem-aws3v3-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.