kfoobar/laravel-kivra

Maintainerscaution

Only one registry account has publish access. That is a limited publishing base and increases continuity risk when combined with the lack of subsequent releases.

Release historycaution

This is the only release, published about five months and three weeks ago, so there is little evidence of sustained maintenance or release follow-through.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, consistent with a project that has been inactive for much of its roughly five-month history.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured, leaving less automated coverage for dependency and code risks.

Security policycaution

The repository has no security policy, so there is no documented route for reporting vulnerabilities or explaining the project's security response.