Package Health/umd-lib/umdds_dynamic_components

umd-lib/umdds_dynamic_components

This is a small, recently established Drupal module with clear licensing, a matching repository, organization backing, a focused dependency set, no deprecation, and no risky lifecycle scripts or GitHub workflow patterns. However, it has only two releases over about 110 days, no tests or changelog in either the artifact or repository, no recent commit activity recorded, no security policy or scanning, and negligible repository adoption; these gaps make its maintenance maturity and ongoing support less certain. It is potentially usable, but should be adopted with normal safeguards and attention to future maintenance activity.

Latest 1.0.1

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health checks

Package scaffolding

A substantial README documents the module's purpose, requirements, installation, and usage, but neither the artifact nor repository contains tests or a changelog. For a small Drupal module this is a genuine maintenance and transparency gap.

Release history

The package is young at about 110 days and has only two releases, so there is limited evidence of sustained release practice or maturity.

Repo commit activity

No commits or active maintainers were recorded in the last three months. Although the repository was recently pushed and the package is young, the absence of observed commit activity limits confidence in ongoing maintenance.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. This may reflect a small, quiet project, but it provides little evidence of active community maintenance.

Repo popularity

The repository has zero stars, forks, and watchers, offering no external adoption evidence. This is a supporting concern rather than a decisive health problem for a small organization-specific module.