spryker-feature/merchant-order-threshold

Repo bus factorcaution

All 2 recent commits came from one release bot, giving a 100% top-contributor share. The organization-owned repository provides maintenance capacity beyond the observed individual contributor, but recent human contributor diversity is not demonstrated.

Repo commit activitycaution

Only 2 commits were recorded in the last 3 months, so recent development activity is modest. The recent release and current repository push provide some compensation, keeping this from being a severe maintenance concern.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool was detected. This is a transparency and process gap, not evidence that the package is unsafe.

Security policycaution

No repository security policy was found. For a maintained open-source package, this reduces transparency about vulnerability reporting and handling.

Token permissionscaution

The only workflow lacks top-level token permissions, so its permissions are not explicitly restricted at that level. No top-level write permissions were detected, but the missing declaration is a workflow-hygiene gap.