hmayer/enum-field

Release historydanger

The package has only two releases, with the latest published on May 5, 2023 and none in the last 12 months. This long release gap is a meaningful maintenance concern for a framework integration.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since May 2023. This materially raises the risk that compatibility fixes will not arrive.

Project backingcaution

The repository is owned by the same individual namespace as the package, providing consistent ownership context. It is user-backed rather than organization-backed, so there is no broader team capacity shown.

Repo popularitycaution

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these values provide no external adoption or community-maintenance cushion for an inactive project.

Repo toolingcaution

Composer is used for the build, which fits the package ecosystem, but no security scanning tools are configured. The missing scanning is a hygiene gap rather than evidence of maliciousness.