mediawiki/guzzle-json-auth

Release historydanger

Only three releases exist, with none in nearly eight years and a median interval of about 641 days. This is strong evidence of abandonment risk, despite the repository not being archived.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release gap and indicating no observed ongoing maintenance.

Repo popularitycaution

The repository has zero stars, forks, and watchers, providing no supporting evidence of adoption or an active user community. Popularity is only supporting evidence, so this reinforces rather than decides the concern.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting expectations unclear. This is a transparency gap, though it is less significant than the inactive maintenance history.

Version stabilitycaution

Version 0.1.2 is not a stable-major release, so the package has limited maturity signals. This matters more alongside the prolonged lack of releases.