Nuget package vulnerable flag misuse

[AndersBillLinden]

Some packages, fortunately only a few, tag an old version of a package as vulnerable (just because it is old).

In this way, we receive warnings that are unnecessary because the project isn't less secure if the only concern is upgrading to the newest version.

We encounter this issue with the Npgsql package (Postgres support).

Package developers need to push new versions differently.

Perhaps the vulnerability flag should be accompanied by a link to a security breach forum thread, as it otherwise loses its value.