Personal verified repositories
Go to file
2023-02-01 01:20:48 +01:00
repositories Add github.com/Benjamin-Loison/YouTube-operational-API 2023-02-01 00:54:58 +01:00
README.md Add default template to README.md introducing status and comment optional fields 2023-02-01 01:20:48 +01:00

Personal verified repositories

This repositories has two aims:

  • as the 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

Note that by repository state I mean the actual state of a repository at a given commit id, so marking a repository at a given commit as verified doesn't mean that previous commits were also verified. Only the resulting state at the given commit id was verified.

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.

Default template:

{
    // Mandatory: git state hash verified.
    "commit": "0123456789abcdef0123456789abcdef01234567",
    // Optional (default: "VERIFIED"): xor of following flags (written as `FLAG_0 | FLAG_1 | ... | FLAG_N`):
    // - `CLOSED_SOURCE_DEPENDENCY`
    // - `UNVERIFIED_INITIAL_COMMIT`
    "status": "VERIFIED",
    // Optional (default: ""): verifier comment concerning the git state verified
    "comment": ""
}