ipdata/api-client

Clear documentation, tests, licensing, and lightweight dependencies make this easy to evaluate and integrate. The small release history and quiet recent development leave maintenance continuity less certain.

Latest 0.1.2

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has existed for about 6 years and 7 months but has only 3 releases, with a median interval of about 3 years. One release in the last 12 months is some evidence of continued maintenance, but the overall cadence is sparse.

Repo commit activity

There were 0 commits and 0 active maintainers in the last 3 months. Combined with the sparse release history, this is a meaningful maintenance-continuity concern.

Security policy

No security policy was found in the repository. This is a transparency gap for reporting and handling vulnerabilities, though it is not evidence that the package is unsafe.

Version stability

Version 0.1.2 is not a prerelease, which is positive, but the package remains below a stable major version and may still carry compatibility risk for consumers.

Workflow audit

Both workflows were analyzed successfully with no high- or medium-severity findings and no untrusted checkout or script-injection sinks. However, all 14 action references are unpinned, weakening build reproducibility and update safety.