spryker/category-image

spryker/category-image 1.6.0 appears to be a healthy, actively maintained dependency. It has a long release history since 2019, a stable non-prerelease version, no registry deprecation, an unarchived organization-owned repository with recent commits from five equally contributing maintainers, and complete package documentation, tests, changelog, licensing, and source alignment. The main reservations are the relatively infrequent release cadence, absence of a repository security policy, and a CI workflow without explicitly declared top-level token permissions; these are transparency and hardening gaps rather than evidence of abandonment, and the workflow analysis found no dangerous patterns.

Latest 1.6.0Packagist

Health Score Breakdown

Repo toolingcaution

The repository uses Composer build tooling, but no security scanning tools were detected. The build setup is present; the missing security tooling is a modest hardening gap rather than a health failure.

Security policycaution

No SECURITY.md or equivalent security policy was found, reducing vulnerability-reporting transparency. The repository's active organization backing and other maintenance evidence partly offset this gap, but do not eliminate it.

Token permissionscaution

The one CI workflow has no top-level permissions declaration. Although no top-level write permissions were detected and dangerous workflow patterns were absent, explicit least-privilege permissions would provide stronger CI hardening.

View all 19 health checks

Vulnerabilities

We didn't find any vulnerabilities for this package.

Direct Dependencies

Dependency	Last Release	Score
spryker/kernel Version ^3.30.0	—	—
spryker/locale Version ^3.1.0 || ^4.0.0	—	—
spryker/category Version ^4.11.0 || ^5.0.0	—	—
spryker/transfer Version ^3.27.0	—	—
spryker/propel-orm Version ^1.0.0	—	—

View All 7 Dependencies