spryker/cms-slot

Release historycaution

The package has existed for about 7 years and has 12 releases, but only one release was published in the last 12 months. That is a modest maintenance concern despite the very recent latest release.

Repo issue activitycaution

There were no new or merged pull requests in the last month, and issue counts are incomplete. This is limited evidence of current community activity, but it is outweighed by recent commits and release activity.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a security-hygiene gap, though it does not by itself indicate poor package maintenance.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a transparency gap for a maintained package.

Token permissionscaution

The only workflow lacks top-level token permissions, so its GitHub Actions permissions are not explicitly restricted in the repository metadata. This is a workflow-hardening gap, although no write permissions were observed.