Package Health/se7enxweb/ezplatform-standard-design

se7enxweb/ezplatform-standard-design

Healthy and usable for developers already adopting the Ibexa DXP stack. It has a long release history, recent publication, tests, licensing, and a matching source repository; the main caveats are a very small public footprint and incomplete workflow permission hardening.

Latest v4.0.0-alpha2

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Dangerous workflows

One of five workflows uses pull_request_target, which requires careful handling of untrusted pull requests even though no untrusted checkout or script injection was detected.

Project backing

The registry namespace and repository are owned by the same individual account, so the package has direct ownership alignment but no organization backing or broader institutional maintainer evidence.

Repo issue activity

There were no new issues or pull requests in the last month and no merged pull requests, indicating limited recent community activity. The absence of open-issue data makes this signal only a moderate concern.

Repo popularity

The repository has only 2 stars, no forks, and no watchers. This is weak supporting evidence and limits external validation, but popularity alone does not make a small specialized package unhealthy.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools were detected. This is a transparency and maintenance gap rather than evidence that the release is unsafe.