jq/response

The package is small, documented, tested, and has no install-time scripts or deprecation notice. Its only release was over five years ago, with no recent commits and minimal repository adoption, so future fixes and compatibility work are unlikely.

Latest v1.0

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

There has been only one release, published over five years ago, with no releases in the last 12 months. This is strong evidence of an inactive project, although the stable v1.0 status limits version churn risk.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the one-release history, this points to a strong abandonment risk.

Project backing

The package is backed by an individual repository owner rather than an organization, and the available activity shows no recent maintenance. There is no organizational capacity visible to offset that gap.

Repo popularity

The repository has one star, one fork, and no watchers. Popularity is only supporting evidence, but these very low figures provide little evidence of community support.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance gap, not a severe risk by itself.