Package Health/scancode/setting-client-module

scancode/setting-client-module

Consumers get little documentation, and the package has no security policy or meaningful repository adoption. Its stable major version, small dependency surface, and lack of install scripts are positives, but they do not offset the transparency gaps.

Latest v2.0.0

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was in June 2020, with zero releases in the last 12 months despite the package being over six years old. This is strong evidence of abandonment risk, although the package is not formally deprecated.

License

No registry license declaration, license file, or repository license file was detected. That leaves the legal terms for using the dependency unclear.

Package scaffolding

The artifact has no README, tests, or changelog, and the repository also reports none. Missing tests and changelogs are acceptable packaging gaps, but the absent README weakens consumer transparency for a module library.

Project backing

The repository owner is a user account rather than an organization, so the available backing signal does not show organizational support. This provides little compensating evidence for the package's thin maintenance record.

Repo package mention

The repository name does not match the package name, and no README mention was available. A name mismatch can be normal for a sub-package, but without a README reference the package-to-repository relationship is less transparent.