rimksky/config

Its four-file footprint and single maintainer leave little evidence of validation or succession. The MIT license, clear README, and no install scripts reduce adoption friction, but they do not offset the long maintenance gap.

Latest v0.1.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in June 2017, with no releases in the last 12 months. That long release gap is strong evidence of abandonment risk despite the package having five historical releases.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since June 2017.

Maintainers

The registry has one publishing maintainer, and the linked repository is owned by the same individual. That is not inherently unhealthy, but it leaves limited visible succession capacity for an otherwise inactive project.

Package file tree

The package and repository each contain only four files, including one source file. This small footprint may fit a minimal utility, but provides little evidence of testing, documentation depth, or ongoing project development.

Security policy

The repository has no security policy. For a small library this is a transparency gap rather than a severe risk, but it gives users no documented channel or process for reporting security issues.