kodicms/laravel-api

Release historydanger

The latest release was published nearly 10 years ago, with no releases in the last 12 months. Six releases show some initial history, but the long silence strongly indicates abandonment risk.

Repo commit activitydanger

The repository had zero commits and zero active maintainers during the last three months, consistent with the release gap and providing no evidence of current maintenance.

Repo issue activitycaution

There were no new or closed issues or pull requests in the last month, while two issues remain open. This adds to the maintenance concern but is weaker evidence than the prolonged release and commit inactivity.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. That is a modest transparency and maintenance gap rather than a severe dependency risk.

Security policycaution

The repository has no security policy. For a Laravel API package, this reduces transparency around vulnerability reporting and response, with no provided evidence compensating for the gap.