fond-of-spryker/customer

Release historydanger

The latest registry release was in March 2020, with no releases in the following six years. That long release gap materially raises abandonment and compatibility risk despite the package having eight releases overall.

Repo commit activitydanger

There were no commits and no active maintainers in the measured three-month period. Combined with the old latest registry release, this points to weak current maintenance capacity.

Repo toolingcaution

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

Security policycaution

The repository has no published security policy. That limits disclosure guidance and is a genuine maintenance-transparency gap, though it is less significant than the inactive release and commit history.