tpetry/laravel-postgresql-enhanced

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months. Because this is a direct maintenance signal, it materially lowers confidence despite the recent release history.

Maintainerscaution

Only one account has registry publishing access. That is a limited publishing base for an individually owned project and increases reliance on one person, although the repository shows substantial project maturity.

Repo issue activitycaution

There are 11 open issues but no new or closed issues and no pull requests in the last month. This suggests limited recent interaction, though it is less concerning than a long-term absence of releases.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning reduces supply-chain hygiene, though it is not evidence that the package is unsafe by itself.

Security policycaution

The repository has no SECURITY.md or other detected security policy. This leaves vulnerability-reporting and response expectations unclear.