ejetar/laravel-http-status-code-utils

Release historydanger

This is the only release, published about 5 years and 7 months ago, with no releases in the last 12 months. That strongly raises abandonment risk, despite the stable 1.0.0 version.

Repo commit activitydanger

The repository has recorded no commits and no active maintainers in the last 3 months, consistent with the long release pause. No newer activity is provided to offset that concern.

Package scaffoldingcaution

The package has no README, which matters for a library consumers must integrate; the absence of tests and a changelog is normal for published artifacts and is not penalized here.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. This is a modest transparency and maintenance gap, not evidence that the package is unsafe.

Security policycaution

The linked repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a secondary governance gap alongside the stronger inactivity concern.