The repository is licensed, tested, and clearly matches the package, with organization backing. Maintenance evidence is limited: no commits in the last three months and no release in over six years.
58%
Total Score
75
88
50
The package has had no registry release in over six years and none in the last 12 months, which is a meaningful maintenance concern. Its four-release history and existing 1.1.0 release provide some maturity evidence but do not offset the long gap.
The repository recorded zero commits and zero active maintainers in the last three months, limiting evidence of ongoing maintenance. The repository's non-archived status and 2024 push provide only partial compensation.
Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency and hygiene gap rather than evidence that the release is unsafe.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This lowers transparency but is not by itself evidence of abandonment.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/money Version ^1.0.0 || ^2.0.0 | — | — |
spryker/sales Version ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0 || ^9.0.0 || ^10.0.0 || ^11.0.0 | — | — |
spryker/guzzle Version ^2.2.0 | — | — |
spryker/kernel Version ^3.0.0 | — | — |
spryker/locale Version ^1.0.0 || ^2.0.0 || ^3.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.