All packages should be signed by default #740

Closed
opened 2026-01-29 14:44:25 +00:00 by claunia · 2 comments
Owner

Originally created by @thompson-tomo on GitHub (May 30, 2025).

To improve the developer ecosystem all nuget packages should be signed and the strong named version deprecated on nuget.org.

With this change, any downstream application/library benefits.

Originally created by @thompson-tomo on GitHub (May 30, 2025). To improve the developer ecosystem all nuget packages should be signed and the strong named version deprecated on nuget.org. With this change, any downstream application/library benefits.
claunia added the question label 2026-01-29 14:44:25 +00:00
Author
Owner

@xoofx commented on GitHub (May 30, 2025):

The package already exists here

@xoofx commented on GitHub (May 30, 2025): The package already exists [here](https://www.nuget.org/packages/Markdig.Signed)
Author
Owner

@thompson-tomo commented on GitHub (May 30, 2025):

@xoofx please read my description:

all nuget packages should be signed and the strong named version deprecated on nuget.org.

I am aware that there is a strong named version but the dual package approach fractures the eco-system hence it should be consolidated into just 1 package.

Hence this issue to address this and as such it ain't done.

@thompson-tomo commented on GitHub (May 30, 2025): @xoofx please read my description: > all nuget packages should be signed and the strong named version deprecated on nuget.org. I am aware that there is a strong named version but the dual package approach fractures the eco-system hence it should be consolidated into just 1 package. Hence this issue to address this and as such it ain't done.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/markdig#740