jstedfast / jstedfast/EmailValidation

Code Sign release artifacts

Open
#119 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
296
Forks
75
PR merge metrics
No merged PRs in 30d

Description

Similar to: https://github.com/jstedfast/MailKit/issues/1882

The release artifact is not code signed. Would consider Code Signing the releases?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the linked MailKit issue and inspecting this repository’s release-artifact process; the issue names no files, workflow, signing tool, or certificate setup. Clarify the target artifacts and signing approach with the maintainer, then verify that published releases are signed and independently verifiable.

Written by the indexing model from the issue text.

Assessment

Domain
release, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.