spryker/agent-security-merchant-portal-gui

Repo popularitycaution

The repository has zero stars and forks and four watchers, which provides little external validation; this is only a supporting caution because organizational backing and active development are present.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected; this leaves a modest repository hygiene gap for a security-related module.

Security policycaution

No repository security policy was found, leaving vulnerability-reporting guidance undocumented; active maintenance and CI provide only partial compensation.

Token permissionscaution

The CI workflow has no top-level token-permissions declaration and does not explicitly declare read-only access, so its permission boundary is less transparent than it should be.