getpop/api-rest

This release appears to be a healthy, actively maintained dependency: it has a five-year history, 162 releases, 33 releases in the last 12 months, a stable non-prerelease version, recent repository activity, an unarchived organization-owned repository, tests, a clear license, and a correctly matching repository reference. The main concerns are that all 15 recent commits came from one contributor, the repository has very little public popularity, and it has no security policy or security-scanning tooling. These are meaningful transparency and resilience gaps, but they do not outweigh the strong release and maintenance evidence.

Latest 19.2.4

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one account has registry publish access. This is a modest publishing-resilience concern, although the linked repository is organization-owned and shows active development.

Repo bus factor

One contributor made all 15 commits in the last 3 months, creating a concentrated maintenance risk. Organization ownership provides some handoff capacity, but no second active contributor is shown.

Repo issue activity

There were no new or closed issues and no pull requests during the last month, with zero open pull requests. This is not inherently unhealthy for a small stable package, but it offers limited evidence of community review.

Repo popularity

The repository has only 2 stars, 0 forks, and 1 watcher. Popularity is supporting evidence rather than a verdict, but these counters provide little independent evidence of broad community adoption.

Repo tooling

Composer is used as a build tool, but no security-scanning tools are configured. The build setup is appropriate, while the missing scanning capability is a modest security-hygiene gap.