spryker/stock

This release appears healthy and suitable to depend on: it has a long release history, a current stable version, recent release activity, an active non-archived organization-owned repository, six active maintainers with low contributor concentration, matching repository/package identity, tests, changelog, and clear package structure. The main concerns are transparency and CI hardening: no security policy or repository security-scanning tool was detected, and the workflow does not declare top-level token permissions. These are meaningful hygiene gaps but are outweighed by the strong maintenance, backing, provenance, and artifact evidence.

Latest 8.17.0

Packagist

88%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo issue activity

There were no new or merged pull requests in the last month and no issue movement was recorded; this is limited recent collaboration evidence, but it is not sufficient to outweigh the observed commit activity and recent release.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected; this is a repository hygiene gap rather than evidence of abandonment.

Security policy

No security policy was detected in the linked repository, leaving vulnerability reporting and disclosure expectations less transparent.

Token permissions

The repository's workflow does not declare top-level token permissions. No write-enabled top-level permissions were observed, but explicit least-privilege configuration would provide stronger CI hardening.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

No maintainer information available.

Direct Dependencies

Dependency	Last Release	Score
spryker/event Version ^2.0.0	—	—
spryker/store Version ^1.5.0	—	—
spryker/touch Version ^3.0.0 \|\| ^4.0.0	—	—
spryker/kernel Version ^3.77.0	—	—
spryker/product Version ^5.0.0 \|\| ^6.0.0	—	—