Package Health/dv-team/openai-chatgpt-api

dv-team/openai-chatgpt-api

This is a promising but very young package with strong basic hygiene: it has an MIT license, README, tests, substantial documentation and examples, no install-time lifecycle scripts, a stable non-prerelease version, an active non-archived repository, and workflows without the analyzed dangerous patterns. The main adoption risks are limited history (only two releases over 48 days), zero recorded repository popularity, and a single contributor responsible for all five commits in the last three months; the missing security policy and undeclared workflow token permissions are additional transparency and hardening gaps. Organization backing and recent activity reduce, but do not eliminate, the bus-factor and abandonment concerns.

Latest 1.0.1

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is only 48 days old and has two releases, so there is not yet enough release history to establish long-term maintenance or compatibility stability.

Repo bus factor

One contributor made all five recent commits, creating a significant single-maintainer dependency risk. The organization-owned repository provides some potential handoff capacity, so this remains caution rather than danger.

Repo popularity

The repository has zero stars, forks and watchers, providing no community adoption evidence. Because popularity is supporting evidence rather than a verdict, this is a caution rather than a severe risk.

Repo tooling

Composer build tooling is present, but no security-scanning tooling was detected. The build setup is positive while the missing automated security checks is a modest hardening gap.

Security policy

No repository security policy was found, reducing transparency about vulnerability reporting and response procedures.