palanik/lumen-cors

Release historydanger

The package has only three releases and none in the last 12 months; its latest release was nearly nine years ago. This is strong evidence of abandonment for a dependency that may need framework compatibility updates.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. The inactive project provides little evidence that compatibility issues will be addressed.

Maintainerscaution

Only one registry maintainer is listed, creating a thin publishing base. The repository is user-owned rather than organization-backed, so there is no provided evidence of broader maintenance capacity to offset that risk.

Repo toolingcaution

Composer is used as the build tool, which fits the package ecosystem. No security scanning tools are present, a minor transparency gap that is outweighed by the more substantial maintenance concerns.

Security policycaution

The repository has no security policy. For a small middleware package this is a modest transparency gap, but it adds little confidence that vulnerability reporting and response are defined.