christoph-kluge/bref-sqs-laravel

Release historydanger

The latest registry release was about four years ago, with no releases in the last 12 months. The repository was pushed later, but the stale release cadence still raises maintenance risk for a production dependency.

Maintainerscaution

Only one registry publisher is listed, so publishing continuity depends on a thin maintainer base. The repository is user-owned rather than organization-backed, with no provided evidence of broader publishing support.

Repo commit activitycaution

There were no commits or active maintainers in the last three months. The November 2024 push shows some later activity, but current development momentum remains weak.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap rather than evidence of an unsafe release.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.