zubarus/zpdo

The implementation is very small and has no tests or security policy, limiting confidence in future changes. MIT licensing, minimal dependencies, organization backing, and no install-time scripts reduce adoption concerns.

Latest v1.0.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

The artifact has no README or tests, but tests and changelogs are not expected in published package artifacts; release notes document this exact initial release. The missing README still limits consumer guidance for a library wrapper.

Release history

This is the only release, published about 11 months ago, with no subsequent releases. That limited history makes ongoing maintenance uncertain for a dependency.

Repo commit activity

There were no commits and no active maintainers in the last 3 months. Combined with the single-release history, this is a meaningful maintenance concern.

Repo popularity

The repository has zero stars, forks, and watchers. This is weak supporting evidence, but popularity alone does not establish that a small package is unsafe to depend on.

Repo tooling

The repository uses Composer build tooling, but no security scanning tool was detected. The missing scanning is a modest transparency and hygiene gap.