azure-oss/identity

This is a usable but relatively young package with a healthy release cadence, stable 1.0.4 versioning, an active and non-archived repository, an organization owner, a clear license file, and no install-time lifecycle scripts. Adoption still carries meaningful maintenance and transparency risk because all 11 recent commits came from one contributor, the package and repository contain no tests, and the repository has no security scanning or security policy. The evidence supports caution rather than abandonment, particularly because the project is only 174 days old and has released five times during that period.

Latest 1.0.4

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The package and repository include a substantial README and changelog, but neither contains tests. For an authentication library, the absence of tests is a genuine maintenance and regression risk.

Repo bus factor

Only one contributor made all 11 commits in the last 3 months, creating a high bus-factor risk. Organization ownership provides some handoff potential, but no second active contributor is evidenced.

Repo issue activity

There were no new or closed issues or pull requests in the last month, while the open issue and pull-request counts are unknown. This provides little evidence of community review or support activity, but does not outweigh the recent commits and releases.

Repo tooling

Composer build tooling is present, but no security-scanning tool is configured. The missing scanning reduces repository hygiene and assurance for an authentication package.

Security policy

No security policy was found in the repository. For a package handling credentials and tokens, this is a meaningful disclosure and vulnerability-response gap.