renocms/user-settings

Usable with caveats: the package is backed by the matching Reno CMS organization and is not deprecated or archived, but it has had no commits in about four months. Documentation and security-maintenance coverage are also thin, so confirm it fits your needs before adopting it.

Latest v0.1.3

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The published artifact has no README, while the repository also reports no tests or changelog. Missing tests and changelog are not expected in every published artifact, but the lack of consumer documentation is a genuine usability and transparency gap for a CMS integration package.

Release history

The package is young, with four releases over about 10 days, but no release has appeared since May 8, roughly four months before collection. That short history and subsequent silence leave maintenance continuity uncertain.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last three months, despite the package being only about 140 days old. This is the strongest evidence of possible maintenance slowdown.

Repo tooling

Composer build tooling is present, but no security scanning tools are reported. That is a maintenance and transparency gap, though it is not by itself evidence that the package is unsafe.

Security policy

The repository has no security policy. This weakens vulnerability-reporting transparency, although the package is organization-backed and the absence is not independently severe.