spryker/currency

Repo toolingcaution

The repository uses Composer build tooling, but no security-scanning tools were detected. This is a transparency and preventive-control gap, though it is not evidence of unsafe code by itself.

Security policycaution

The organization-backed repository has no published security policy, leaving vulnerability reporting and response expectations less transparent.

Token permissionscaution

The only workflow does not declare top-level token permissions. No write permissions were detected, but explicit least-privilege settings would provide stronger CI safety.