Package Health/umd-lib/umdlib-design-system-theme

umd-lib/umdlib-design-system-theme

This release appears suitable to depend on: it is actively maintained, with 13 releases in the last 12 months, a stable non-prerelease version, 45 commits from three active contributors in the last three months, and a non-archived repository that matches the package and references it in the README. The Apache-2.0 declaration, modest runtime dependency set, absence of install-time scripts, and organization backing are positive. The main reservations are concentrated commit activity, with one contributor responsible for 80% of recent commits, and limited project hygiene: no tests, changelog, security policy, or security scanning tools were observed. These concerns reduce transparency and resilience but do not indicate abandonment, especially given the recent release and commit activity.

Latest 4.0.4

Packagist

84%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health checks

Package scaffolding

A README is present and documents installation and required modules, but neither the artifact nor repository contains tests or a changelog. For a Drupal theme this is a meaningful, though not severe, transparency and verification gap.

Repo bus factor

Recent work is concentrated in one contributor at 80% of commits, creating some continuity risk; however, two additional contributors were active, and organization ownership provides some capacity to hand off maintenance.

Repo popularity

The repository has only 3 stars and 4 forks, indicating limited external adoption, but popularity is supporting evidence and does not outweigh the observed maintenance activity.

Repo tooling

Composer is used as a build tool, but no security scanning tools are configured. The build tooling is appropriate, while the missing security automation is a hygiene gap rather than a severe health issue.

Security policy

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.