gent-drupal/gent_base

This release appears generally safe to depend on from a supply-chain health perspective: it has a long history since 2018, 90 releases, 19 releases in the last 12 months, a stable non-prerelease version, an active non-archived organization-backed repository, a clear GPL license, and a documented security policy. The main concerns are that repository commit activity shows no commits or active maintainers in the last 3 months, the repository has no tests, and no security-scanning tooling was detected; these reduce confidence in ongoing maintenance and verification but are partly offset by the very recent release and repository push activity, changelog, and substantial source tree.

Latest 7.3.8

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Lifecycle scripts

post-install-cmd and post-update-cmd scripts run during Composer operations, increasing installation complexity and requiring review, but this is consistent with the README's documented Drupal theme setup workflow.

Package scaffolding

A substantial README and changelog are present, but neither the artifact nor repository contains tests. For a Drupal theme this is a maintenance gap, though the documentation and changelog provide useful transparency.

Repo commit activity

No commits and no active maintainers were recorded in the last 3 months, which raises a maintenance concern; however, the package had a release and the repository was recently pushed, so this is not by itself evidence of abandonment.

Repo popularity

The repository has modest adoption signals with 6 stars, 3 forks, and 6 watchers. This is limited supporting evidence but is not itself a health problem for a specialized theme.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. The missing scanning coverage is a transparency and verification gap rather than a direct health verdict.