robertlemke/rss

The package is small and straightforward to consume. MIT licensing, a README, release notes, and no install-time scripts reduce adoption friction, but future fixes may depend on the sole maintainer.

Latest 2.1.1

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

One registry maintainer is responsible for publishing the package, creating a thin publishing base. The linked repository is also owned by the same individual, so there is no demonstrated organizational backing to offset that concentration.

Release history

The latest release was published about four years ago, with no releases in the last 12 months. This is a meaningful maintenance concern, although the package has a stable history of six releases since 2015.

Repo commit activity

The repository recorded no commits and no active maintainers in the last three months, consistent with the long release gap. The inactive project is not archived, but there is no recent evidence of ongoing work.

Repo issue activity

There has been no issue or pull-request activity in the last month, while one issue and one pull request remain open. This provides limited evidence of current support or responsiveness.

Security policy

The linked repository has no security policy, which reduces transparency about how vulnerabilities should be reported. This is a hygiene gap rather than evidence that the package is unsafe.