intothesource/laravel-faq

Release historydanger

Only one release exists, published nearly 11 years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a package intended as a Laravel dependency.

Repo commit activitydanger

The repository has recorded no commits and no active maintainers in the last three months, consistent with the nearly 11-year release gap. The linked repository is present, but there is no observed maintenance activity.

Repo popularitycaution

The repository has only 2 stars and no forks, providing little evidence of community adoption or external validation. Popularity is supporting evidence rather than a verdict, so this is a secondary concern.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, especially alongside the long period without updates.

Version stabilitycaution

Version 0.0.1 is an early, non-stable release and the package has never progressed beyond it. The absence of a prerelease marker does not compensate for this very immature version history.