The README and release notes make integration straightforward, and the package has a long, stable release history. It has no install-time scripts, while the organization-backed project remains actively published.
68%
Total Score
67
50
94
75
The feature declares 33 runtime dependencies, which is a substantial dependency surface for consumers. This is understandable for an aggregate Spryker feature, but it increases upgrade and transitive-risk burden.
One contributor made all four recent commits, creating concentrated maintenance capacity. Organization backing provides some handoff potential, but no second active contributor is shown.
Four commits were recorded in the last three months, showing recent activity, but all were made by one maintainer.
Composer build tooling is present, but no security-scanning tooling is reported. This is a modest transparency and maintenance-hygiene gap, not evidence of unsafe behavior.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/company Version ^1.9.0 | — | — |
spryker/company-gui Version ^1.10.0 | — | — |
spryker/company-role Version ^1.13.0 | — | — |
spryker/company-user Version ^2.23.0 | — | — |
spryker/company-role-gui Version ^1.12.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.