besnik/customized-bred

Release historydanger

The package has had no release in the last 12 months, and its latest release was over three years ago. Four releases in total show limited ongoing maintenance for a Laravel integration package.

Repo commit activitydanger

There were zero commits and zero active maintainers during the last three months, consistent with the package's long release gap and indicating a substantial abandonment risk.

Repo package mentioncaution

The repository name matches the package, but its README does not mention the package name. That weakens package-to-source transparency, though the matching repository name provides partial context.

Repo popularitycaution

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but this provides no community signal to compensate for the inactive maintenance record.

Repo toolingcaution

Composer build tooling is present, but no security scanning tool was detected. This is a hygiene gap that matters for a package handling application administration functionality.