trin4ik/laravel-devino-api

Release historydanger

The latest release was about five years ago, with no releases in the last 12 months. Eleven releases show some history, but the long release gap is a substantial abandonment concern.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, while its last push was nearly four years ago. This provides little evidence of ongoing maintenance.

Repo popularitycaution

The repository has zero stars and forks and only one watcher, offering little supporting evidence of community review or adoption. Popularity is supporting evidence, so this does not determine the verdict alone.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest hygiene concern rather than evidence that the package is unsafe.

Security policycaution

The repository has no security policy. This is a transparency and response-process gap, though it is less serious than the lack of recent maintenance.