shippinno/oauth2-next-engine

Release historycaution

The package has only one release, published more than nine years ago, with no releases in the past 12 months. This is meaningful abandonment risk for a dependency despite the repository remaining available.

Repo commit activitycaution

There were no commits and no active maintainers in the past three months. Combined with the single old release, this weakens evidence of ongoing maintenance.

Repo popularitycaution

The repository has only 1 star and 1 fork, indicating a small user and contributor footprint. Popularity is supporting evidence rather than decisive, but this provides little external validation.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are reported. The missing scanning is a hygiene gap, not evidence that the package is unsafe.

Security policycaution

The repository has no security policy. For an OAuth-related library, this reduces transparency about vulnerability reporting and maintenance response.