Package Health/abhisingh159/inflow-cloud-php-sdk

abhisingh159/inflow-cloud-php-sdk

This is a usable but immature package with a clear MIT license, a focused dependency profile, a non-deprecated release, and a repository that matches the package and was recently pushed. However, it is only 101 days old, remains on the unstable 0.x line, has no tests or changelog, has no security scanning or security policy, and shows zero commits or active maintainers over the last three months despite recent publication activity. The single-user ownership and lack of repository popularity provide little evidence of maintenance resilience, so adoption is reasonable for bounded use but carries meaningful continuity and quality risk.

Latest v0.1.3

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

The repository reports zero commits and zero active maintainers during the last three months. This is a significant maintenance-risk signal, even though the repository was pushed recently and the package has recent releases.

Maintainers

Only one registry account has publish access, which creates a limited publishing and continuity base. The repository is user-owned rather than organization-backed, so there is no provided organizational evidence to offset that limitation.

Package file tree

The small, coherent 16-file tree is understandable and focused on SDK source and resources, but it contains no tests or other supporting project files, limiting evidence of engineering maturity.

Package scaffolding

A substantial README documents requirements, configuration, and usage, but neither the artifact nor repository contains tests or a changelog. For an SDK, the absence of tests is a meaningful quality and maintenance gap.

Project backing

The package is backed by a matching repository owned by the same individual user, which establishes source continuity but offers less institutional backing and redundancy than an organization-owned project.