ernestdefoe/google-fonts

Healthy and suitable to install, with modest transparency and security-process gaps. It is actively maintained, has two recent contributors, and is not deprecated or archived; the main concerns are no tests, no security policy, and a workflow with write permissions.

Latest 0.2.4

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health checks

Maintainers

Only one registry publisher is listed, which is a limited publishing backup for a user-owned project. Repository activity from a second contributor provides some compensating maintenance evidence.

Package scaffolding

A substantial README and GitHub Releases are present, but neither the package nor repository includes tests or a changelog. The missing tests reduce confidence in maintenance quality, while releases partly compensate for the missing changelog.

Project backing

The registry namespace and repository are owned by the same individual, so the package has direct ownership alignment but no organization-level backing or evident handoff capacity.

Repo popularity

The repository has one star and no forks or watchers, indicating little external adoption or review. Popularity is supporting evidence only, so this lowers confidence modestly rather than making the package unfit.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. The build setup is adequate for the package, while the missing scanning is a modest process gap.