codyjheiser/laravel-db2-eloquent

Maintainerscaution

One registry maintainer is consistent with a user-owned project, but it provides limited continuity if that person becomes unavailable. The repository's recent inactivity makes this thin maintainer base more relevant.

Project backingcaution

The repository is owned by the same individual namespace as the package, rather than an organization. This matches the single-maintainer evidence and provides direct ownership alignment, but no organizational continuity.

Repo commit activitycaution

There were 0 commits and 0 active maintainers during the last three months, despite a recent release. The lack of recent source activity raises maintenance and abandonment risk.

Repo popularitycaution

The repository has 1 star, 0 forks, and 0 watchers, indicating very limited external adoption or review. Popularity is supporting evidence rather than a verdict, but this leaves little community backup.

Repo toolingcaution

The repository uses Composer, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not a severe risk on its own.