epttavm/api-client

The MIT license, small dependency surface, and package README help with adoption. The linked organization repository is genuine, but its limited security and maintenance practices increase long-term ownership risk.

Latest 1.0.6

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases exist, with the latest published in October 2016 and none in the last 12 months. This is strong evidence of an abandoned release line.

Repo commit activity

There were no commits or active maintainers in the last three months, consistent with the repository having been inactive for about eight years. This materially raises abandonment risk.

Repo issue activity

Four issues remain open, with no new or closed issues and no pull-request activity in the last month. The small backlog is not severe, but it shows no recent maintenance response.

Repo tooling

Composer is used for the build, but no security scanning tools are configured. The missing scanning is a hygiene gap rather than proof of unsafe code.

Security policy

The repository has no security policy. This weakens vulnerability-reporting transparency, especially for a client library integrating with an external service.