jorisros/iptools

Its small, tested codebase has a clear MIT license, README, and no install-time scripts. The long period without releases or recent commits makes future fixes and compatibility work uncertain, while unpinned workflow actions add a smaller maintenance risk.

Latest v1.4

Packagist

45%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no releases in the last 12 months, and its latest release was about 8 years ago. That strongly raises abandonment and compatibility risk despite the five-release history.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the old release history, this is strong evidence that maintenance has stalled.

Maintainers

One registry maintainer is consistent with the repository being owned by an individual, but it leaves little visible publishing redundancy if that person stops maintaining the project.

Project backing

The registry namespace and repository are owned by the same individual, which supports package identity but provides no organizational backing to compensate for the stalled activity.

Repo popularity

The repository has 1 star and 0 forks, indicating limited external adoption and review. Popularity is supporting evidence only, but this provides little compensating community signal.