sisoft/gs1_barcode

Release historydanger

The package has only one release, published about seven years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a library dependency.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the old last push, this indicates no current maintenance capacity.

Project backingcaution

The linked repository is owned by an individual account rather than an organization, and the registry namespace differs from the repository owner. This offers limited visible backing for long-term maintenance.

Repo issue activitycaution

There are no open issues or pull requests and no recent issue or pull-request activity. While this avoids unresolved work, it also provides no evidence of an active maintenance community.

Repo popularitycaution

The repository has zero stars, one fork, and one watcher. Popularity is not decisive by itself, but these very low adoption signals provide little evidence of active community support.