ahmetbarut/pixabay

No tests or security policy provide little evidence of ongoing care. The single maintainer and minimal repository activity further limit confidence, so adoption carries meaningful abandonment risk.

Latest 1

Packagist

40%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only one release, published about six years ago, with no releases in the last 12 months. This is strong evidence of stalled maintenance for a dependency.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with a project that has stopped receiving maintenance.

Project backing

The repository is owned by the same individual namespace as the package, which supports package identity but does not provide organizational maintenance capacity.

Repo popularity

The repository has zero stars and forks and only one watcher, indicating minimal adoption and limited visible community support. Popularity is supporting evidence rather than a verdict, but it reinforces the maintenance concerns.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. This is a moderate transparency and maintenance gap for a dependency with no recent activity.