spryker/form-extension

Release historycaution

Only one release exists, published about 6 years and 10 months ago, which limits evidence of registry maintenance. Recent repository commits and organizational backing partly compensate for that stale release history.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected; this is a minor transparency and hygiene gap rather than a dependency-blocking risk.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations unspecified. This is a minor transparency gap for an otherwise actively maintained project.

Workflow auditcaution

The sole workflow was fully analyzed with no audit findings or untrusted-code sinks. Two of four action references are unpinned, which is a modest reproducibility and supply-chain hygiene concern.