mjaschen/oauth2-mtbnews

Release historydanger

The latest release was published nearly nine years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a dependency that may need compatibility updates.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long gap since the latest release. No provided signal shows renewed maintenance.

Repo popularitycaution

The repository has zero stars and forks and only one watcher. Popularity is not decisive, but these figures provide little supporting evidence of community oversight.

Repo toolingcaution

Composer is used for builds, but no security-scanning tooling is present. This is a hygiene gap that adds some uncertainty, though it is less significant than the inactivity evidence.

Security policycaution

The repository has no security policy. For a small, inactive OAuth client, this reduces transparency and leaves no documented route for reporting security issues.