baethon/tailwind-class-collapse

Release historycaution

The package has only one release, published more than six years ago, with no releases in the last 12 months. That leaves current compatibility and maintenance uncertain.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months. Combined with the single-release history, this is meaningful evidence of limited ongoing maintenance.

Repo popularitycaution

The repository has one star, one fork, and one watcher. This is limited supporting evidence of adoption, but popularity alone does not determine health.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene gap rather than evidence of abandonment.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations unclear. This lowers transparency but is not severe enough to make the release unfit on its own.