frankkessler/guzzle-oauth2-middleware

Release historydanger

The package has only two releases, with the latest published in October 2016 and none in the last 12 months. This long release gap is a strong abandonment concern for a dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the past three months, consistent with the package's long release silence. No provided maintenance signal compensates for this.

Repo toolingcaution

The project uses Make and Composer, showing basic build tooling, but it has no detected security scanning. This is a minor transparency and maintenance gap rather than a standalone severe risk.

Repository archivedcaution

The linked repository is not archived, which avoids the strongest abandonment signal, but its last push was in July 2019 and does not offset the absence of recent commits.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. The package's age and lack of activity make this gap more consequential.