proshore/site-setting

Release historydanger

The package has had no release in more than eight years, with only four releases overall and none in the past 12 months. This is strong evidence of abandonment risk for a Laravel integration package.

Repo commit activitydanger

There were no commits and no active maintainers in the past three months, consistent with the package having been inactive since 2018. This materially increases abandonment and compatibility risk.

Maintainerscaution

The registry lists one maintainer, and the repository is organization-owned, so the short registry list is not inherently concerning. However, the absence of recent commits shows no current maintenance capacity in practice.

Repo popularitycaution

The repository has zero stars and one fork, providing little evidence of broad community use or review. Popularity is supporting evidence only, but it offers no compensating signal for the stale maintenance record.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a minor transparency and hygiene gap, secondary to the much older activity record.