nkf/example-api-client

Project backingcaution

The repository is owned by an individual user rather than an organization, so there is no organizational backing shown by this signal. This is a modest capacity concern for a package with no recent activity.

Release historycaution

The package has only two releases, both published about two years ago, with no releases in the last 12 months. This indicates a largely inactive release history, though it is not by itself evidence of abandonment.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months, consistent with a repository that has seen no meaningful recent development. The repository was last pushed about two years ago, making this a material maintenance concern.

Repo popularitycaution

The repository has zero stars and forks and one watcher. This is weak supporting evidence for maturity, but popularity alone does not determine whether a small package is dependable.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tooling was detected. The missing scanner is a hygiene gap rather than a severe risk because other repository signals are available.