Why not D10?

Problem/Motivation

I really like what this module does to help users understand managed vs. unmanaged files. While we are starting our D10->D11 upgrades, we won't be done with these before the EoL/EoY. This feature would be extremely useful to our organization as some previous staff members leveraged their access to Acquia and Pantheon to upload files to Drupal sites on a regular basis.

I thought you may be using features that only exist in D11, but this is what GitHub CoPilot had to say...

Strictly speaking, none of the module’s business functions are specific to Drupal 11. File scanning, status classification, batching, deletion, Media importing, Forms, Views integration, and service injection all use general Drupal APIs.

The module is Drupal-11-only because of its metadata:

composer.json: requires drupal/core: ^11 and drupal/core-dev: ^11

I updated the info.yml to all ^10 || ^11 and everything seems to work, but I'm not that familiar with the module's features.

Other than the pending EoL, was there a reason you didn't include D10 support? Would you consider merging an MR to add it? While it's possible to patch in D10 support, it requires creating a custom repo in Composer as the official release will never be recognized as a valid dependency for a D10 site.