emirustaoglu/barcode

Usable with caveats: the package is clearly licensed, documented, tested, and backed by a matching repository, but it is brand new with no established release or commit history. A single maintainer and no security policy add uncertainty for a library with no demonstrated maintenance track record.

Latest 1.0.0

Packagist

64%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

One registry maintainer is consistent with an individually owned project, but it leaves little visible publishing redundancy if that maintainer becomes unavailable.

Project backing

The registry namespace and repository owner match, and the project is owned by an individual rather than an organization; this supports a genuine project link but offers limited institutional backing.

Release history

This is the first release and the package is zero days old, so there is no track record for release stability or long-term maintenance.

Repo commit activity

The repository has recorded zero commits and zero active maintainers in the last three months; because the package was just created, this mainly reflects limited history rather than confirmed abandonment, but it still provides no maintenance evidence.

Repo popularity

The repository has no stars, forks, or watchers. This is weak supporting evidence rather than a standalone health failure, especially for a new package.