programster/pgsql-lib

Tests, a clear MIT license, and a stable major release improve transparency. The two-release history, no recent commits, and uncertain repository linkage make long-term support difficult to verify.

Latest 2.0.0

Packagist

52%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases have been published, with no release in about 2 years and 6 months and a median interval of about 2 years and 3 months. This suggests slow maintenance and lowers confidence in ongoing support.

Repo commit activity

There were no commits and no active maintainers in the last 3 months. Combined with the old last push, this is evidence of currently inactive maintenance.

Repo package mention

The repository name does not match the package name and its README does not mention the package. That weakens confidence that the linked source repository belongs to this release.

Repo popularity

The repository has 1 star, 0 forks, and 1 watcher. This is limited supporting evidence, though popularity alone is not required for a small stable package.

Repo tooling

The repository uses Composer build tooling, which fits the package ecosystem, but no security scanning tools were detected. For this small library, that is a modest hygiene gap rather than a severe risk.