Figure 1. Where the second person sits in a typical open source release
- 1. Commit1 author
- 2. Review and merge2 people: branch protection
- 3. Tag or release1 maintainer or botbee-js bypass: an unsigned commit that never went through a pull request was tagged v13.3.0 and released. Step 2 never saw it.
- 4. Buildautomated in CI
- 5. Publish1 maintainer, bot, or tokenxz utils: part of the backdoor existed only in the release tarball, never in the reviewed git history.
- 6. Installwhat consumers run
Solid heavy border: step with a second person. Dashed box: an attack that went around it.
