Safety check release bug

[dokazhi]

Describe the bug
Safety check says 6.0b1 is more secure version

To Reproduce
How can we reproduce the problem? Please be specific. Don't just link to a failing CI job. Answer the questions below:

1. What version of Python are you using?
2. What version of coverage.py are you using? The output of coverage debug sys is helpful.
3. What versions of what packages do you have installed? The output of pip freeze is helpful.
4. What code are you running? Give us a specific commit of a specific repo that we can check out.
5. What commands did you run?

Expected behavior
A clear and concise description of what you expected to happen.

Additional context
Add any other context about the problem here.

[danuker]

As you can see, version 6.0b1 is the latest released right now, so if you want security to stop complaining, you should perhaps update.

Alternatively, you can ignore this issue with -i 41002 as arguments for safety, if your organization does not see coverage using MD5 as a risk (which I doubt it does, unless you need to be blindly FIPS compliant like the guy that asked for this change here).

Personally, I think this is a bug in safety, because I don't see how the coverage tool could be tricked with a hash collision into exploiting any system.
Edit: it seems somebody else agrees.

[nedbat]

This is a duplicate of #1198.