pr2apisdk/sdk

Usable with caveats: the package is licensed, documented, tested, and not archived, but its last registry release was nearly four years ago and recent repository activity is absent. A single publisher and no security policy add maintenance risk.

Latest v1.0.2

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

There have been only four releases, all concentrated in November 2022, with no release in nearly four years. That is a meaningful sign of stagnation for a dependency expected to receive compatibility and maintenance updates.

Repo commit activity

The repository had no commits and no active maintainers in the last three months, consistent with a project whose registry releases have stopped and increasing abandonment risk.

Maintainers

Only one registry account has publishing access, creating limited release continuity if that maintainer becomes unavailable. The repository is user-owned, so there is no organization backing shown to compensate for the thin publisher base.

Repo popularity

The repository has no stars or forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counters provide little evidence of a broad community that could sustain the project.

Repo tooling

Composer is used as the build tool, but no security scanning tool is configured. The missing scanning is a transparency and maintenance gap, not evidence that the package is malicious.