hatchetaustralia/laravel-iam-db-auth

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months. Combined with the old latest release, this is meaningful evidence of stalled maintenance.

Project backingcaution

The repository is owned by a personal GitHub account rather than an organization, so the small registry maintainer base is not clearly compensated by organizational backing.

Release historycaution

The package has only three releases and none in the last three years, with a median interval of about 440 days. This indicates slow maintenance and lowers confidence in timely fixes.

Repo popularitycaution

The repository has zero stars, one fork, and one watcher, indicating very limited visible adoption. A small package can still be healthy, so this is supporting caution rather than a standalone verdict.

Repo toolingcaution

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