The package has organization backing, regular releases, and a clear README with release notes. Recent work comes from one contributor, while all four workflow actions are unpinned and no security policy or scanning is present.
73%
Total Score
67
100
88
67
The manifest declares a proprietary license, and both the package and repository contain a LICENSE file. The release is therefore licensed, though the proprietary terms may restrict reuse compared with a permissive open-source license.
One contributor made all two commits in the last three months. Organization backing reduces the risk somewhat, but no second active contributor is shown, so recent maintenance remains concentrated.
The repository had two commits in the last three months, showing recent activity, but the volume is modest for the assessment period.
Composer is used for builds, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence of abandonment.
The repository has no security policy. That leaves vulnerability-reporting and response expectations undocumented, which modestly lowers transparency.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/sales-reclamation Version ^1.3.0 | — | — |
spryker/sales-reclamation-gui Version ^2.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.