football/football-data

Release historydanger

Only two releases exist, with none in the last 12 months and a latest release about five years ago. This is strong evidence of abandonment risk for a package intended for ongoing API integration.

Repo commit activitydanger

There were no commits or active maintainers in the last three months, despite the repository being available. This indicates maintenance has effectively stopped.

Maintainerscaution

Only one registry account has publish access. That is a thin publishing base and leaves limited continuity if the maintainer becomes unavailable.

Project backingcaution

The repository is owned by an individual user rather than an organization, so there is no visible organizational backing to compensate for the thin maintainer base.

Repo issue activitycaution

There are no open issues or pull requests and no activity in the last month. Combined with the stale release and commit history, this supports an abandonment concern.