Package Health/heimrichhannot/contao-tinymce-bundle

heimrichhannot/contao-tinymce-bundle

This release is generally usable, with a six-year history, 16 releases, six releases in the last 12 months, a recent latest release, an unarchived repository, an organization-backed project, and clear package/repository alignment. Its main concerns are that repository commit activity shows no commits and no active maintainers in the last 3 months, the repository has very little visible adoption, the artifact and repository contain no tests, and the repository lacks a security policy and explicit workflow token permissions. These are meaningful maintenance and transparency gaps, but they are partly offset by the recent release cadence, changelog, CI workflow, clean workflow-risk profile, and absence of install-time scripts.

Latest 0.4.5

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A README and changelog are present, and the repository has a changelog and GitHub Releases, but neither the package nor repository contains tests. The documentation is adequate for a small bundle, while the missing tests leave a maintenance-quality gap.

Repo commit activity

There were 0 commits and 0 active maintainers in the last 3 months, which is a concrete short-term maintenance concern. The recent release history and repository push provide partial compensation, so this is caution rather than danger.

Repo popularity

The repository has 1 star, 0 forks, and 3 watchers. Popularity is only supporting evidence, but these very low figures provide little independent evidence of broad community adoption.

Repo tooling

Composer build tooling is present and the repository includes CI-related configuration, but no security scanning tools are reported. The tooling baseline is reasonable for the package, with a security-hygiene gap.

Security policy

No repository security policy is present. For a small package this is not independently disqualifying, but it reduces transparency around vulnerability reporting and maintenance practices.