networkteam/json-seq

Clear licensing, tests, documentation, and a minimal dependency set make integration straightforward. The repository is small and has no recent issue or commit activity, while its organization backing and stable release offset some abandonment concern.

Latest v1.1.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only four releases since July 2018, with no release in about three years and none in the last 12 months. That is a meaningful maintenance concern for a dependency, though the package may be intentionally stable.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the last push being about three years ago. This is the strongest evidence of possible abandonment.

Repo issue activity

There are no open issues or pull requests and no recent issue activity. This is not inherently negative for a small stable library, but it provides no evidence of active maintenance.

Repo popularity

The repository has only two stars, no forks, and no watchers. Popularity is supporting evidence rather than a verdict, but these counts provide little independent confidence or community resilience.

Repo tooling

Composer build tooling is present, but no security scanning tool was detected. The missing scanning is a modest repository-hygiene gap, not evidence that the release is unsafe.