kharanenka/laravel-scope-date

Release historydanger

The package has released only once, on November 12, 2016, with no releases in the last 12 months. That long release gap is strong evidence of abandonment risk.

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last 3 months, consistent with the lack of releases and indicating no observable ongoing maintenance.

Repo issue activitycaution

There has been no new or closed issue or pull-request activity in the last month. This supports the maintenance concern, although the absence of open issues limits how strongly it weighs on its own.

Repo popularitycaution

The repository has 1 star and no forks, providing little community evidence or fallback support. Popularity is only supporting evidence, so this is a secondary concern rather than a verdict.

Security policycaution

The repository has no security policy, reducing transparency about how vulnerabilities are reported and handled. The small, inactive project provides no compensating security process in the collected signals.