Package Health/localgovdrupal/localgov_content_lock

localgovdrupal/localgov_content_lock

The repository has had no commits or releases for about 19 months, and it lacks a security policy and security scanning. It is a small, tested Drupal module with clear licensing, but the published replacement should be preferred.

Latest 1.0.1

Packagist

30%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Registry deprecation

Packagist marks the entire package abandoned and names drupal/localgov_content_lock as its replacement. This is a direct adoption risk even though the release itself is not individually withdrawn.

Release history

Only two releases exist, with the latest published about 19 months ago and no releases in the last 12 months. The short history and prolonged release gap provide little evidence of ongoing maintenance.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Although a small stable module may need few changes, this still leaves current maintenance capacity unproven.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest supply-chain hygiene gap rather than evidence of an unsafe release.

Security policy

The linked repository has no security policy. That reduces transparency for reporting and handling vulnerabilities, particularly for a package that modifies Drupal content-locking behavior.