ubxty/azure-ai

Documentation, licensing, tests, and a clear package layout support adoption. The missing security policy and concentrated contribution pattern leave more continuity risk than a mature project would normally carry.

Latest 2.2.7

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The registry namespace and repository owner match, but both belong to a user account rather than an organization. This supports ownership consistency but provides limited evidence of institutional maintenance capacity.

Repo bus factor

One contributor made 23 of 24 recent commits, or about 96%, while the second made one. The active second contributor partly offsets the concentration, but continuity still depends heavily on one person.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing automated security checks are a transparency and maintenance weakness, not a severe risk by themselves.

Security policy

The repository has no security policy. For a package handling cloud API credentials, this leaves vulnerability-reporting expectations less clear.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Ubxty

Direct Dependencies

Dependency	Last Release	Score
ubxty/core-ai Version ^2.2	—	—
illuminate/http Version ^11.0\|^12.0\|^13.0	—	—
illuminate/cache Version ^11.0\|^12.0\|^13.0	—	—
illuminate/console Version ^11.0\|^12.0\|^13.0	—	—
illuminate/routing Version ^11.0\|^12.0\|^13.0	—	—