Other package managers use code signing to help ensure package integrity and authenticity.
The idea is that package consumers can be sure of
a) that the package has not been modified by anyone other than the author (Integrity)
b) the package is actually from the author (Authenticity)
c) that the package actually comes from where it says it does (Provenance).
NuGet uses code signing, both by the package author and by the repo and you can configure the client to decide what/who to trust.
Package signing should not be required for packages or package submission, as this would discourage many from submitting packages due to the cost and effort required to get a code signing certificate.
Other package managers use code signing to help ensure package integrity and authenticity.
The idea is that package consumers can be sure of
a) that the package has not been modified by anyone other than the author (Integrity)
b) the package is actually from the author (Authenticity)
c) that the package actually comes from where it says it does (Provenance).
NuGet uses code signing, both by the package author and by the repo and you can configure the client to decide what/who to trust.
Package signing should not be required for packages or package submission, as this would discourage many from submitting packages due to the cost and effort required to get a code signing certificate.