Skip to content

Conversation

@mcevoy-building7
Copy link

Part 1 of SLSA edits from Seth McEvoy.
Branch: front-matter
Files:
about.md - About SLSA -standard edits: smooth and clarify technical complexity.
slsa-terms.md - SLSA Terminology - combined single terminology gathered and alphabetized from all tracks.

Ignore other files in this branch for now.

Please review but do not merge. We need to create a workflow for editing feedback.

Thanks!

@netlify
Copy link

netlify bot commented Dec 22, 2025

Deploy Preview for slsa ready!

Name Link
🔨 Latest commit 9cb6f06
🔍 Latest deploy log https://app.netlify.com/projects/slsa/deploys/69560644b4ed21000818f37c
😎 Deploy Preview https://deploy-preview-1533--slsa.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

---
title: About SLSA
description: With supply chain attacks on the rise, a shared vocabulary and universal framework are needed to provide incremental guidance to harden supply chains for more secure software production. This page introduces the main concepts behind SLSA and explains how it can help anyone involved in producing, consuming, or providing infrastructure for software.
title: About SLSA
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: I don't think we want these extra spaces at the end of these lines?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Markdown doesn't care but some of the other tools might care. I don't know.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just ran the linter on these files, and this space is indeed not a problem. But we did get several other linter errors we may want to resolve once all edits are done.

mcevoy-building7 and others added 8 commits December 23, 2025 01:56
Co-authored-by: Tom Hennen <TomHennen@users.noreply.github.com>
Signed-off-by: Seth McEvoy <mcevoy.building7@gmail.com>
Co-authored-by: Tom Hennen <TomHennen@users.noreply.github.com>
Signed-off-by: Seth McEvoy <mcevoy.building7@gmail.com>
Copy link
Contributor

@marcelamelara marcelamelara left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @mcevoy-building7 ! I've left several comments in the About doc and will send reviews for the other files soon.

public, disruptive, and costly in today's environment when exploited. These attacks have also shown that there are inherent risks not just in code itself, but at
multiple points in the complex process of getting that code into software
systemsthat is, in the **software supply chain**. Since these attacks are on
systems; that is, into the *software supply chain*. Since these attacks are on
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The "into" here, I think, changes the meaning of this sentence. What this sentence was trying to convey is that the "the complex process of getting that code..." is the software supply chain. Maybe the misleading part is actually "getting that code into software systems" because it's an uncommon description of what happens in the software supply chain.

I wonder if a simplification like this could work here: "multiple points in the the complex process of creating and distributing that code as software; that is, the software supply chain"

Comment on lines +46 to +47
analysis and review performed on the source code still applies to
the binary consumed after the build and distribution process is complete.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not entirely sure where, but I feel like there's a comma missing somewhere here.

@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in Issue triage Jan 6, 2026
@mcevoy-building7
Copy link
Author

These files will be split into new pull requests. Sorry!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants