The package includes tests, a clear MIT license, and an organization-owned repository. Its workflow uses three unpinned actions and the project lacks a security policy, adding maintenance hygiene concerns.
61%
Total Score
75
88
50
The latest release was nearly three years ago, with no releases in the last 12 months. This weakens confidence in ongoing maintenance, although the package has an established release history.
There were no commits and no active maintainers in the last three months. This is a meaningful maintenance concern, though it is less severe because the repository is not archived and has recent historical activity.
The repository uses Make and Composer build tooling, but no security scanning tools were detected. This is a modest transparency and maintenance gap.
No security policy was found in the repository. This does not establish a security defect, but it reduces transparency about vulnerability reporting and handling.
The sole workflow was fully analyzed with no trigger or audit findings, but all three referenced actions are unpinned. That leaves avoidable build-integrity risk and is a hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
spryker/country Version ^3.0.0 || ^4.0.0 | — | — |
spryker/oms-extension Version ^1.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.