Herein lies the issue.
Your library addresses issues that you personally have perceived exist with licensing software.
What you haven't done is ascertain what issues actually exist.
For example, what problem does your library alleviate?
There are other examples out there that can also be used for free, so it's not that.
There are examples that work natively across multiple environments, like Mac, Linux and Windows. Again, your library doesn't help there.
Java, C++, Swift etc.? Nope.
Centralized auditing? Cryptographically secure? Battle tested?
Sadly your local library strikes out everywhere - it's very core sadly let's it down because you didn't actually identify a problem to address, so your "solution" isn't really going to move a needle.
Multiple questions have been asked of you but nowhere have you really identified the audience for this library.
Why should someone use it over something else?
There's 100s of similar packages available on Nuget - many of them seemingly unmaintained.
For your library to be of use, you need to offer value over the cruft and crud.
Open source is a blessing and a curse. I've multiple packages out there that I thought were pretty neat at the time - and filled a niche spot. Few folk felt the same but that's fine by me as well.
Rather than try to iterate on this, I'd step back and ask yourself the hard question: what does your lib do better (or at least equally as well) as the competition?
And be severely critical. Given the stated purpose of this library, put yourself in the mind of an adversary: how quickly could you defeat it? If it's mere minutes then it's not good enough.
Look for all the weaknesses, look how other libraries fix the weaknesses.
In the end you may decide to give up. That's fine as well. Don't treat it as failure though, just use it as a stepping stone and try, try again.