spryker-feature/product-offer-service-points-availability

Repo bus factorcaution

One contributor made all 3 commits in the last 3 months, creating concentrated activity. The organization-owned repository provides some handoff capacity, so this is a concern rather than a severe risk.

Repo commit activitycaution

There were 3 commits in the last 3 months, showing recent activity, but the pace is modest for an actively maintained project. The recent release history partly compensates for that limited commit volume.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. That weakens automated assurance without indicating abandonment by itself.

Security policycaution

The repository has no security policy. This is a transparency and vulnerability-reporting gap, though it does not by itself show that the release is unsafe.

Workflow auditcaution

The single workflow was fully analyzed with no untrusted checkouts, injection findings, or high-severity audit findings. However, all 4 action references are unpinned, leaving build inputs less reproducible and harder to control.