laravel-shield/bitbucket-server

Release historydanger

There has been only one release, published nearly nine years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a dependency expected to track its ecosystem.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers during the last three months, consistent with the long release gap. No provided maintenance signal compensates for this inactivity.

Name lookalikecaution

The package borrows the identity of the much more established laravel/dusk, but its artifact overlap is low and its README identifies it as a Bitbucket Server driver rather than a copy. This still warrants caution about name confusion.

Repo popularitycaution

The repository has zero stars and zero forks, with only two watchers. Popularity is supporting evidence rather than a verdict, but these counts provide little evidence of a broad active user or contributor base.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools are reported. This is a modest hygiene gap and does not outweigh the maintenance evidence.