mslwk/otomoto-scrapper

Release historydanger

Only two releases were published, with none in the last 12 months; the latest release was over seven years ago. This is strong evidence of abandonment risk for a package that may need to track changes in its scraped service.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with the repository's last push being in January 2019. This materially increases abandonment risk.

Maintainerscaution

A single registry publishing account is consistent with a user-owned project, but it offers little redundancy if that maintainer becomes unavailable.

Project backingcaution

The repository is owned by an individual user rather than an organization, so the single registry maintainer and small contributor base provide no visible organizational backing.

Repo issue activitycaution

There are no open issues or pull requests, but there has also been no recent issue or pull-request activity; this does not demonstrate active maintenance.