Skip to content

Commit

Permalink
Update docs/proposals/source-verificiation-policies.md
Browse files Browse the repository at this point in the history 
Co-authored-by: Michael Crenshaw <350466+crenshaw-dev@users.noreply.github.com>
Signed-off-by: Jann Fischer <jann@mistrust.net>
  • Loading branch information
@jannfis @crenshaw-dev
jannfis and crenshaw-dev committed May 10, 2024
1 parent 25933d6 commit bbd5b5e
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/proposals/source-verificiation-policies.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -246,7 +246,7 @@ Implementing this proposal would significantly increase resilience against breac

### Risks and Mitigations

The new verification levels (i.e. `progressive` and `full`) make source verification a lot more robust and thorough compared to the current implementation.
The new verification levels (i.e. `progressive` and `strict`) make source verification a lot more robust and thorough compared to the current implementation.

However, for `progressive` mode, there are at least two risk factors I can see which I'd like to raise for validation:

Expand Down

0 comments on commit bbd5b5e

Please sign in to comment.