chp/textcontent

Release historydanger

The package has had no releases in the last 12 months, and its latest release was in March 2017—over nine years ago. This is strong evidence of abandonment risk, despite the 12-release history.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with the old last push, this materially raises the risk that defects and compatibility issues will go unaddressed.

Dependency profilecaution

Six runtime dependencies create a meaningful compatibility and maintenance surface for a package that has not been updated since 2017. No development dependencies are declared, so the published metadata gives little evidence of a maintained verification setup.

Project backingcaution

The repository is owned by an individual account rather than an organization, so the single registry maintainer provides limited visible backing for long-term maintenance.

Repo toolingcaution

Composer is used for builds, but no security scanning tools are present. That is a maintenance and transparency gap, though it is less serious than the demonstrated inactivity.