yven/openai-php-client

A clear README, tests, MIT licensing, and a matching repository make adoption easier. The small release history, absent recent commits, missing security policy, and unpinned workflow actions leave maintenance and build-integrity concerns.

Latest 1.0.1

Packagist

45%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The package and repository are owned by the same individual account, so the matching ownership is transparent, but it does not provide organizational backing to offset the thin maintenance history.

Release history

The package has only two releases, both within about one day, and no releases in the last 12 months despite being about 16 months old. This indicates limited demonstrated maintenance.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with roughly 16 months since the last push. That is a meaningful abandonment concern for a client library.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a hygiene gap, not evidence of a security failure by itself.

Security policy

The repository has no security policy, leaving vulnerability reporting and response expectations unclear for a package that handles API integrations.