jiny/config

Usable with caveats: the package is clearly backed by an organization, licensed, documented, and not deprecated or archived. However, it has had no release in about 19 months and no repository commits in the last 3 months, so maintenance should be verified before adopting it.

Latest 0.9

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has eight releases over about 2 years, but none in the last 12 months; the latest release was published about 19 months ago. This indicates a meaningful maintenance slowdown.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months. Combined with no releases in the last year, this is the clearest evidence of currently limited maintenance.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. This is consistent with a small package, but it provides little evidence of active community maintenance.

Repo tooling

Composer is used as the build tool, but no security scanning tools are configured. The absence of scanning is a hygiene gap, not evidence that the package is unsafe, and the repository has no workflows that would amplify this concern.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This lowers transparency but is not by itself evidence of abandonment.