spryker/gui-table

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. The build setup is appropriate, while the missing security automation is a modest repository-hygiene weakness.

Security policycaution

The repository has no security policy. This reduces vulnerability-reporting transparency and is a genuine hygiene gap, although it does not indicate abandonment by itself.

Token permissionscaution

The only workflow lacks top-level permissions declarations, and no workflow has explicit read-only permissions. This leaves token access less constrained than ideal, though there are no detected dangerous workflow patterns.