Package Health

spryker/content-gui

Healthy and suitable to depend on. It has a long release history, recent releases, active multi-contributor maintenance, a matching source repository, tests, and clear licensing; the main caveat is limited repository security-policy and workflow-permission hygiene.

Latest 3.2.0PackagistPackagist

88%

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

100

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

94

Supply Chain
Supply Chain
Evaluates supply chain security practices and risks

75

Health Score Breakdown

Repo toolingcaution

The repository uses Composer build tooling, but no security-scanning tool was detected. This is a modest transparency gap, not evidence that the package is unsafe by itself.

Security policycaution

No repository security policy was found, leaving vulnerability-reporting expectations undocumented. The organization backing and active maintenance partly compensate, but the gap remains relevant.

Token permissionscaution

The repository's only workflow lacks top-level token permissions, so its GitHub Actions privilege boundary is not explicitly documented. No top-level write permissions were detected.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

No maintainer information available.

Direct Dependencies

DependencyLast ReleaseScore
spryker/gui
Version ^4.0.0 || ^5.6.0
spryker/kernel
Version ^3.32.0
spryker/locale
Version ^3.2.0 || ^4.0.0
spryker/content
Version ^2.0.0
spryker/symfony
Version ^3.2.0

Weekly Downloads

Info

Last Published
6 days ago
Created
7 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