Package Health/emulsify-ds/emulsify-design-system

emulsify-ds/emulsify-design-system

This release has strong maturity and transparency indicators: it is a stable 7.x release from a package with nearly seven years of history, 56 releases, nine releases in the last 12 months, an explicit GPL license, substantial documentation, and a non-archived organization-backed repository with read-only CI permissions and no dangerous workflow patterns. However, the package is explicitly marked abandoned on Packagist with a replacement package, and the linked repository shows no commits or active maintainers in the last three months despite the recent release timestamp. The repository also does not match the package name or mention it in its README, creating package-to-source transparency risk. These concerns make adopting this package a liability unless the replacement package is unsuitable or migration is not feasible.

Latest 7.2.2

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Registry deprecation

Packagist marks the package as abandoned and names emulsify-ds/emulsify-drupal as its replacement. This is a severe adoption and maintenance-risk signal for a dependency, regardless of the package's recent release history.

Package scaffolding

The artifact contains a substantial README of about 24,299 characters, but neither the package nor the source repository reports a test suite or changelog. The detailed documentation compensates for some of this hygiene gap, but the absence of tests and changelog still reduces transparency.

Repo commit activity

The linked repository recorded 0 commits and 0 active maintainers over the last 3 months. Although the package has a recent release, the observed lack of recent development materially raises abandonment risk.

Repo issue activity

There are only 5 open issues and no new or closed issues or pull requests in the last month. The small backlog is not inherently concerning, but the complete absence of recent issue or PR activity is consistent with slowing maintenance.

Repo package mention

The repository name does not match the package name and its README does not mention the package. This weakens confidence that the linked source repository directly backs this Packagist package, even though the organization context provides some compensation.