Package Health/anomaly/wysiwyg-field_type

anomaly/wysiwyg-field_type

Usable with caveats: it has a long release history, clear MIT licensing, documentation, and an active organizational owner, but recent development has slowed sharply with no commits in the last three months. The missing security policy and limited repository activity warrant review before adopting it for a critical dependency.

Latest v3.2.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has existed for over 11 years with 124 releases and a release as recently as December 2025. However, only one release in the last 12 months suggests a substantially slower current cadence than its historical average.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last three months. This is the strongest concern because it indicates little recent development activity despite the recent release.

Repo popularity

The repository has only 4 stars and 21 forks, indicating a small user base. Popularity is supporting evidence rather than a requirement, and the organizational backing and long release history provide some compensation.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The lack of automated security checks reduces maintenance transparency, though it is not by itself evidence that the package is unsafe.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities in a package that includes upload and media-related functionality.