spryker/development

Repo toolingcaution

Composer build tooling is present, but no security-scanning tooling was detected. This is a modest transparency gap, not a severe dependency-health concern given the active release and contributor history.

Security policycaution

The repository has no published security policy. That weakens vulnerability-reporting transparency, although it is partly offset by active organizational maintenance and a clean workflow audit.

Workflow auditcaution

All one workflow was analyzed successfully with no dangerous triggers, untrusted checkouts, script injection, or audit findings. Two of four action references are unpinned, which is a minor reproducibility gap rather than a severe risk.