spryker/store-context

Repo popularitycaution

The repository has 0 stars and 0 forks, which provides little independent popularity evidence. This is only a supporting concern because recent activity, tests, releases, and organization ownership provide stronger health evidence.

Repo toolingcaution

Composer build tooling is present, but no repository security-scanning tool was detected. This is a modest transparency and assurance gap, not evidence of abandonment.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations undocumented. The gap lowers transparency but is not severe given the active organization-backed project.

Token permissionscaution

The single workflow has no top-level token permissions declaration, so its default permission scope is not explicitly hardened. No write permissions were detected, limiting the concern.