This project is mirrored from Pull mirroring updated .
  1. 07 Jul, 2021 3 commits
  2. 02 Jul, 2021 2 commits
  3. 01 Jul, 2021 4 commits
    • Mark Lodato's avatar
      Convert attacks table to Markdown. · 978bd0c6
      Mark Lodato authored
      This makes the table easier to maintain. Although the long lines are
      annoying, we get the benefit of not having to deal with HTML.
    • Mark Lodato's avatar
      Reformat the attacks table, fix link to reqs. · 69ff74d6
      Mark Lodato authored
      Reformat the attacks table to make it easier to maintain:
      - Remove unnecessary closing `tr` and `td` tags.
      - Merge short columns onto one line.
      - Separate each row with a blank line.
      - Break lines at natural boundaries.
      Fix a stale link to, which (a) was an absolute
      link instead of relative, (b) pointed to a file that has since been
      deleted, and (c) didn't work on since the jekyll-relative-links
      plugin only works on Markdown links, not HTML links.
    • Mark Lodato's avatar
      Merge pull request #86 from MarkLodato/npm · 3713e7da
      Mark Lodato authored
      Set up `npm run lint` to call markdownlint.
    • Mark Lodato's avatar
      Pin GH Actions and rename lint to format · 833d1a5d
      Mark Lodato authored
  4. 30 Jun, 2021 5 commits
  5. 29 Jun, 2021 7 commits
  6. 28 Jun, 2021 3 commits
  7. 25 Jun, 2021 3 commits
    • Tom Hennen's avatar
      Update · 447b5291
      Tom Hennen authored
    • Tom Hennen's avatar
      Update · 269cfe0f
      Tom Hennen authored
    • Tom Hennen's avatar
      Allow a service other than the 'build service' to generate provenance · 5f253fb9
      Tom Hennen authored
      This is just an initial thought.  We might only want this adjustment at L2 but still make the build service generate the provenance at L3+.
      On the other hand, maybe as long as the builder _reports_ the data and it's confident in that data, it would be fine for some other service to generate the provenance?
      That would allow for a 'trusted service' to translate one provenance format to another (in addition to gathering the data from API calls).
  8. 24 Jun, 2021 2 commits
  9. 23 Jun, 2021 7 commits
  10. 22 Jun, 2021 4 commits
    • Mark Lodato's avatar
      Linkify reqs table; remove duplicate descriptions. · bf854aca
      Mark Lodato authored
      In the "Level requirements" section, add links in the table from each
      requirement the corresponding entry in the detailed source/build/common
      doc, and remove the duplicate "summary" descriptions below it. This
      avoids confusion and the need to keep the two in sync, at the cost of
      making it slightly harder to skim. This seems like a worthwhile
      Also convert the table to pure Markdown, for two reasons:
      - To make the table easier maintain.
      - To allow us links to work in both GitHub and GitHub Pages. This is
        achieved by the jekyll-relative-links plugin, which only works with
        markdown links, not HTML links.
      The downside to converting to Markdown is that we can't use rowspan and
      colspan. This isn't too bad of a hit to readability.
    • Mark Lodato's avatar
      Merge pull request #72 from slsa-framework/gh-pages · 3936bd69
      Mark Lodato authored
      Create GitHub Pages and move example to separate page.
    • Mark Lodato's avatar
      Delete 'Next Steps' section. · 8e1f729d
      Mark Lodato authored
      This was out of date and is no longer needed.
    • Mark Lodato's avatar