thisismahabadi/laravel-feature-flags

Release historydanger

The latest release was about four years ago, and there have been no releases in the past 12 months. That long gap materially raises abandonment risk despite nine releases during the initial launch period.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the past three months, consistent with the prolonged release gap and providing no evidence of ongoing maintenance.

Maintainerscaution

One registry maintainer creates a thin ownership base, so there is little visible redundancy if the maintainer becomes unavailable. This reinforces the maintenance concern but is not severe by itself.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap for a package handling application integration.

Security policycaution

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency gap, though it does not by itself make the release unfit.