gsferro/responseview

Release historydanger

The latest release was in April 2023, with no releases in the following about 3 years and 5 months and only three releases overall. This is the strongest sign of possible abandonment, although the package may be stable and is not deprecated.

Maintainerscaution

One registry maintainer is responsible for publishing the package. That is a thin maintainer base for continuity, though the linked repository is owned by the same individual and the package is small.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the long release gap. The repository is not archived, which is a limited compensating signal but does not show active maintenance.

Repo toolingcaution

Composer is used as the build tool, which fits the package ecosystem, but no security-scanning tools are configured. The missing scanning is a modest maintenance and assurance gap rather than a severe risk.

Security policycaution

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This matters for a dependency but is less severe for a small view/controller helper.