The repository has tests, a matching organization-owned project, and a clear MIT license. Workflow references are unpinned and the repository has no recent commit activity, increasing maintenance and build-reproducibility concerns.
58%
Total Score
75
100
81
50
Only two releases have been published, with the latest on January 23, 2023 and none in the last 12 months. This long release gap materially raises abandonment risk for a package that may need compatibility updates.
There were zero commits and zero active maintainers in the last three months. Combined with the old registry release, this points to limited current maintenance capacity.
The repository uses Make and Composer build tooling, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
No security policy was found in the repository. That reduces transparency for reporting and handling vulnerabilities, although it does not by itself show that vulnerabilities exist.
The single workflow was fully analyzed with no audit findings and no untrusted checkout or script-injection paths. However, all 3 of 3 action references are unpinned, leaving build inputs less reproducible.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spryker/sales Version ^11.18.0 | — | — |
fond-of-oryx/customer-registration 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.