jover/ripe-db-query

Its MIT license and single runtime dependency keep the package straightforward to inspect. The single 2016 release and unchanged repository leave no evidence of current maintenance, so adopting it creates abandonment risk.

Latest 0.1.0

Packagist

32%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

100

Health Score Breakdown

Release history

This is the package's only release, published about 10 years ago, with no releases in the last 12 months. That leaves no evidence of an active release process.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months. Combined with the old release history, this strongly indicates the project is no longer maintained.

Package scaffolding

The artifact has no README, tests, or changelog, while the repository also reports none. The missing tests and changelog are normal for a tiny published artifact, but the missing README makes library integration less transparent.

Repo package mention

The repository name does not match the package name, and no README package reference was available. This makes the package's source relationship less transparent, although the mismatch could reflect a separately named project.

Repository archived

The repository is not formally archived, which avoids the strongest abandonment signal, but it was last pushed about 10 years ago and provides little practical reassurance.