aleskafka/data-loader

It has a minimal dependency footprint and includes a license plus repository tests. The source repository is not archived, but it has no security scanning or security policy, adding maintenance uncertainty.

Latest v0.1

Packagist

32%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This package has only one release, published about 10 years ago, with no releases in the last 12 months. That strongly indicates abandonment risk for a dependency.

Repo commit activity

There have been no commits and no active maintainers in the last three months, consistent with a project that has been inactive since March 2016.

Maintainers

Only one registry publishing maintainer is listed. That is not inherently unhealthy for a user-owned project, but it leaves little visible publishing redundancy when combined with the lack of recent activity.

Project backing

The registry namespace and repository are owned by the same individual, providing consistent ownership context. The user-owned project has no organizational backing to compensate for the thin maintenance record.

Repo issue activity

There has been no issue or pull-request activity recently. With no releases or commits either, this supports a picture of an unmaintained project rather than an actively stable one.