spryker/event

Dependency profilecaution

The package has 10 runtime dependencies, mostly related Spryker components and infrastructure libraries. This is a meaningful dependency surface but is coherent for an event module rather than unusually broad.

Repo popularitycaution

The repository has 0 stars and 1 fork, so public adoption evidence is limited. This is supporting evidence only and is outweighed by the package's long release history and current contributor activity.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool was detected. The absence of scanning is a transparency gap, though it is not by itself evidence of unsafe code.

Security policycaution

The repository has no security policy. That weakens vulnerability-reporting transparency, although active maintenance and organization backing partly compensate for the gap.

Token permissionscaution

The single workflow does not declare top-level token permissions and does not explicitly declare read-only permissions. No write permissions were detected, but explicit least-privilege configuration would be clearer.