4leads/php-ninox-api

Its MIT license, clear README, and minimal dependency set help adoption. The lack of a security policy or scanning makes trust and future maintenance harder to assess.

Latest v1.0.2

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only three releases were published, with the latest in February 2021 and none in roughly 5 years and 8 months. This strongly raises abandonment risk for a maintained API client.

Repo commit activity

There were no commits or active maintainers in the last 3 months, consistent with the repository being inactive for about 5 years and 8 months. This is the clearest abandonment concern.

Project backing

The package and repository are owned by the same individual account, 4leads. This is consistent ownership but indicates no visible organizational backing to offset the thin maintenance record.

Repo popularity

The repository has 0 stars, 1 fork, and 1 watcher. Popularity is only supporting evidence, but these figures provide little evidence of broad review or community support.

Repo tooling

Composer is used for builds, but no security scanning tools are configured. This is a modest transparency and maintenance concern rather than a standalone disqualifier.