spryker/customer-extension

This release appears healthy and suitable to depend on: it is a stable, non-deprecated package with a long release history, a recent release, an active non-archived organization-backed repository, current commit activity from five contributors, and balanced contributor participation. The package has a license file, coherent source and artifact structure, no install-time lifecycle scripts, and no detected dangerous workflow patterns. Remaining concerns are the absence of repository security scanning and a security policy, the lack of explicitly declared workflow token permissions, and the absence of tests in both the artifact and repository; these reduce transparency and assurance but do not outweigh the evidence of active maintenance and project backing.

Latest 1.8.0Packagist

Health Score Breakdown

Package scaffoldingcaution

The artifact has a README and changelog, and the repository also has a changelog and uses GitHub Releases. Tests are absent in both places, which is a modest assurance gap for a package providing interfaces.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. The build setup is established while security assurance remains a gap.

Security policycaution

No repository security policy was found, reducing transparency about vulnerability reporting and response procedures.

Token permissionscaution

The repository's only workflow lacks top-level token permissions. No write permissions were observed, but explicit least-privilege configuration is still absent.

View all 18 health checks

Vulnerabilities

We didn't find any vulnerabilities for this package.

Direct Dependencies

Dependency	Last Release	Score
spryker/transfer Version ^3.27.0	—	—