opauth/bitbucket

Release historydanger

The latest release was published in March 2013, with no releases in the last 12 months and 3 releases overall. This is strong evidence of abandonment risk for a dependency.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the release history and indicating no current maintenance capacity.

Package file treecaution

The artifact contains GoogleStrategy.php while the linked repository contains BitbucketStrategy.php, suggesting the published package contents and source tree are inconsistent. This weakens release transparency.

Package scaffoldingcaution

The artifact includes a README, which supports consumer use, but its excerpt describes Opauth-Google rather than the Bitbucket strategy. That makes the package documentation materially misleading.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, especially for an authentication-related package.