The module is clearly packaged with a README, changelog, license, and a matching source repository. Organization backing and a stable 1.0.0 release help, but ongoing activity and workflow hygiene remain limited.
55%
Total Score
75
88
83
This is the only release, published about 16 months ago, with no releases in the last 12 months. That leaves maintenance continuity unproven despite the repository remaining available.
There were no commits and no active maintainers in the last three months. This is meaningful evidence of limited recent maintenance, although it does not establish abandonment by itself.
Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance-hygiene gap.
The repository has no security policy. This weakens the project's documented process for reporting and handling vulnerabilities.
The single workflow was fully analyzed with no dangerous triggers or audit findings, but all 4 referenced actions are unpinned. That leaves avoidable build-integrity exposure and is a workflow-hygiene caution.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/kernel Version ^3.75.0 | — | — |
spryker/merchant Version ^3.5.1 | — | — |
spryker/state-machine Version ^2.16.0 | — | — |
spryker/merchant-extension Version ^1.2.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.