From 32263625f54f60a156899cb41e48b196f7cefbc0 Mon Sep 17 00:00:00 2001 From: Benjamin Loison Date: Wed, 1 Feb 2023 00:38:24 +0100 Subject: [PATCH] Precise the current trust level target in `README.md` I thought about adding the following convention: > Current convention is such that if a folder exists but just contains `.gitkeep`, it means that everything that could fall into this folder and isn't existing is considered as verified. This would be useful for personal git users, but it's an edge case and would anyway need to precise an overwhole git user gits hash to confirm a statement at a given gits state. So let's keep the same convention for every git. --- README.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 1be6794..f321a4a 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,9 @@ # Personal verified repositories This repositories has two aims: -- serve as a personal memo to keep track of personal verified states of repositories that *I use* and briefly comment as far as I know their legitimacy - as [the web of trust](https://en.wikipedia.org/wiki/Web_of_trust), people trusting me can trust the repositories states that I verified +- serve as a personal memo to keep track of personal verified states of repositories that *I use* and briefly comment as far as I know their legitimacy + +The current trust level is defined as looking legitimate, I don't guarantee that to the best of my knowledge there isn't any security vulnerability. + +Meta-informations related to a git, such as dependencies (not the legitimate aspect but the verified one), issues, pull requests..., aren't verified yet but may be in the future, if so it would be precised as such.