ckryo/laravel_http

Release historydanger

The latest release was in June 2017, with no releases in the last 12 months despite the package being about nine years old. This is strong evidence of abandonment risk for a framework integration.

Maintainerscaution

Only one account has registry publish access. That is not inherently unsafe, but combined with the old last release it indicates a thin maintenance base.

Package file treecaution

The package and repository each contain only 11 files, covering a small set of helpers, migrations, configuration, and a service provider. The compact scope limits complexity but provides little evidence of mature maintenance practices.

Package scaffoldingcaution

The artifact includes a README, but it is only 11 characters long and there are no repository tests or changelog. The absence of tests and a changelog is a minor concern here; the extremely limited documentation is the material gap.

Project backingcaution

The linked repository is owned by an individual user rather than an organization, so there is no visible organizational backing to compensate for the single registry maintainer and long inactivity.