Package Health/jetcod/laravel-iam-db-auth

jetcod/laravel-iam-db-auth

This release is usable but carries meaningful maintenance risk. It has a valid GPL-3.0-or-later license, a matching organization-owned repository, documentation, changelog, stable versioning, no deprecation, no install-time lifecycle scripts, and a small dependency footprint. However, the package has only two releases across roughly 900 days, no commits or active maintainers in the last 3 months, no tests, no security policy, and no security-scanning tooling. The repository is not archived and was recently pushed, but the lack of recent commit activity and limited release history suggest that adoption should be accompanied by compatibility testing and a willingness to maintain or fork it if Laravel or AWS integration changes.

Latest 1.0.1

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package file tree

The artifact contains a focused source tree, Composer metadata, documentation, changelog, and certificate files, which provides reasonable packaging transparency. The absence of test files in the complete 30-file tree limits confidence in regression protection.

Package scaffolding

A README and changelog are present, and the repository uses GitHub Releases, but neither the package nor repository contains tests. For an authentication and database-connection integration, the missing test coverage is a genuine maintenance concern.

Release history

The package is about 900 days old but has only two releases, with one release in the last 12 months and a median release interval of about 900 days. This indicates a very sparse release cadence and lowers confidence in ongoing maintenance.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last 3 months. This recent collapse in observable development activity is the strongest maintenance concern, although it is partly offset by the repository not being archived and a recent push being recorded.

Repo issue activity

There were no new issues or pull requests in the last month and one merged pull request, indicating limited recent collaboration. The absence of issue counts is unknown rather than negative, so this is only a modest concern.