spryker/payment-data-import

Release historycaution

Only two releases were published, both in December 2019, with no registry release in the last 12 months. This is a meaningful age and release-cadence concern, although recent repository activity provides some compensation.

Repo toolingcaution

Composer is used as the build tool, but no security scanning tools were detected. The missing scanning is a modest transparency gap rather than a severe risk.

Security policycaution

No repository security policy was found. This limits documented vulnerability-reporting transparency, but it does not by itself indicate abandonment.

Workflow auditcaution

The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. Two of four action references are unpinned, leaving a moderate reproducibility and action-integrity gap.