plover/nest-config

Its MIT license, organization backing, and single runtime dependency keep adoption straightforward. The small repository has no security policy or scanning, while recent commit activity is absent and documentation is minimal.

Latest v1.0.2

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact has no README, tests, or changelog. Missing tests and changelog are normal packaging practice, but the absent README modestly reduces consumer guidance for a library.

Release history

Three releases appeared within 10 days, showing an initial release burst, but the latest release is about five months old with no later release evidence.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, leaving weak evidence of ongoing maintenance after the initial release period.

Repo package mention

The repository name does not exactly match the package name, and no README mention was available. This creates some uncertainty that the linked repository is the intended source, although the naming difference is compatible with a sub-package layout.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. That is a hygiene gap rather than evidence that the package is unsafe.