workbuddy/openapi

This is a usable but very immature release: it is only one day old, has a single v0.1.0 release, and shows no commits or active maintainers in the last three months, so maintenance continuity is not yet demonstrated. The package is nevertheless transparent and reasonably structured, with an MIT license and license file, a substantial README, repository tests, Composer-based tooling, no install-time scripts, a non-archived repository, and no detected dangerous workflow patterns. The absence of security scanning and a security policy, together with unspecified workflow token permissions, adds operational caution. Adoption may be reasonable for evaluation or controlled use, but the release should be monitored closely and not treated as a mature dependency.

Latest v0.1.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by an individual user rather than an organization, so the project has a limited visible backing structure and likely depends on a single owner.

Release history

The package is only 1 day old and has exactly one release, so there is no observed release track or history demonstrating sustained maintenance.

Repo commit activity

There were zero commits and zero active maintainers in the last three months; because the project is only 1 day old, this is partly explained by its novelty, but it still leaves maintenance capacity unproven.

Repo popularity

The repository has zero stars, forks, and watchers. This is not a health verdict for a new or specialized package, but it provides no supporting evidence of community adoption.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected, leaving security-process coverage unestablished.