Package Health

spryker/merchant-relation-request-merchant-portal-gui

This release appears suitable to depend on from a maintenance and transparency perspective. It is a stable 2.2.0 release with seven releases over roughly 894 days, a recent release, an active non-archived organization-owned repository, and six commits from six active maintainers in the last three months. The package and repository include substantial source structure, a changelog, licensing information, and matching repository references. The main reservations are the absence of tests, the lack of a security policy, and workflow permissions that are not explicitly constrained; these are hygiene gaps rather than evidence of abandonment, especially given the recent distributed activity and active Spryker organizational backing.

Latest 2.2.0PackagistPackagist

84%

Total Score

Maintainer Stability
Maintainer Stability
Assesses the consistency and reliability of package maintainers

100

Dependencies
Dependencies
Evaluates the health and security of package dependencies

50

Maturity
Maturity
Indicates package age, release frequency, and adoption metrics

88

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

80

Health Score Breakdown

Dependency profilecaution

The package declares 18 runtime dependencies, which is substantial but consistent with a GUI module integrating merchant portal, relation-request, translation, mail, and UI components; this increases integration surface without independently indicating poor package health.

Package scaffoldingcaution

The package has a README and changelog, and the repository also has a changelog and uses GitHub Releases. Neither the artifact nor repository contains tests, which is a maintenance-quality gap for a substantial GUI module.

Repo toolingcaution

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

Security policycaution

The repository has no SECURITY.md or equivalent security policy, reducing vulnerability-reporting transparency. Recent distributed maintenance and organizational backing partly mitigate the concern but do not remove the gap.

Token permissionscaution

The single workflow lacks top-level token permissions, and no workflow declares write permissions. This is less restrictive than an explicit read-only policy, but there is no observed write-enabled workflow to create a severe risk.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

No maintainer information available.

Direct Dependencies

DependencyLast ReleaseScore
spryker/mail
Version ^4.6.0
spryker/twig
Version ^3.0.0
spryker/kernel
Version ^3.30.0
spryker/zed-ui
Version ^4.3.0
spryker/symfony
Version ^3.0.0

Weekly Downloads

Info

Last Published
14 days ago
Created
2 years ago

Are You Affected?

Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.

Free. No credit card required.

Aikido Platform