Benjamin_Loison/Verified_repositories
1
0
Fork 0
Code Issues 5 Pull Requests Packages Projects Releases Wiki Activity

Precise the current trust level target in README.md

Browse Source 
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.
This commit is contained in:
Benjamin Loison 2023-02-01 00:38:24 +01:00
parent fd7ad7a93d
commit 32263625f5
Signed by: Benjamin_Loison
SSH Key Fingerprint: SHA256:BtnEgYTlHdOg1u+RmYcDE0mnfz1rhv5dSbQ2gyxW8B8
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -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.