shredio/auth

Workflow dependencies are unpinned and the repository has no security policy or scanning. Organization backing, repository tests, a clear MIT license, and regular prior releases provide useful safeguards.

Latest 2.1.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months. Although the latest release was on March 11, 2026, the current lack of observed development lowers confidence in ongoing maintenance.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. This is not inherently unhealthy, but it provides no evidence of an active support community.

Repo popularity

The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these very low counts provide little external validation for a security-sensitive authorization package.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. For an authorization library, the missing security automation is a meaningful hygiene gap.

Security policy

The repository has no security policy. That makes the process for reporting and handling vulnerabilities less transparent, especially for an authorization-focused package.