docs: remove SLSA 0.1 from docs and fix tables (#829)

Signed-off-by: behnazh-w <[email protected]>

Author: behnazh-w

README.md

@@ -6,7 +6,7 @@
 
 Macaron is a supply chain security analysis tool from [Oracle Labs](https://labs.oracle.com/pls/apex/r/labs/labs/intro), which focuses on the build integrity of an artifact and the artifact dependencies. It is based on the [Supply chain Levels for Software Artifacts (SLSA)](https://slsa.dev/) specification, which aims at preventing some of the software supply chain attacks as the systems get more complex, especially with respect to the use of open-source third-party code in applications. Attacks include stealing credentials, injecting malicious code etc., and it is critical to have security assurance on the third-party code to guarantee that the integrity of the code has not been compromised.
 
-Macaron uses [SLSA requirements specifications v0.1](https://slsa.dev/spec/v0.1/requirements) to define concrete rules for protecting software integrity that can be checked for compliance requirements automatically. Macaron provides a customizable checker platform that makes it easy to define checks that depend on each other. This is particularly useful for implementing checks for SLSA levels. In addition, Macaron also checks a user-specified policy for a software component to detect unexpected behavior in the build process. We currently support the following build tools:
+Macaron uses [SLSA requirements specifications](https://slsa.dev/spec/v1.0/levels) to define concrete rules for protecting software integrity that can be checked for compliance requirements automatically. Macaron provides a customizable checker platform that makes it easy to define checks that depend on each other. This is particularly useful for implementing checks for SLSA levels. In addition, Macaron also checks a user-specified policy for a software component to detect unexpected behavior in the build process. We currently support the following build tools:
 
 * Maven and Gradle Java build systems
 * Pip or Poetry package managers for Python

docs/source/_static/style.css

@@ -1,6 +1,8 @@
 /* Copyright (c) 2022 - 2022, Oracle and/or its affiliates. All rights reserved. */
 /* Licensed under the Universal Permissive License v 1.0 as shown at https://oss.oracle.com/licenses/upl/. */
 
+/* !important prevents the common CSS stylesheets from overriding
+    this as on RTD they are loaded after this stylesheet */
 .wy-nav-content {
     max-width: 1200px !important;
 }
@@ -9,3 +11,18 @@
 .wy-nav-top {
     background: #464545;
 }
+
+/* The Read the Docs Sphinx theme contains a bug that causes text in table cells not to wrap.
+   This results in very wide tables with horizontal scroll bars.
+*/
+.wy-table-responsive table td {
+    /* The white-space CSS property sets how white space inside an element is handled. */
+    white-space: normal !important;
+}
+
+.wy-table-responsive {
+    /* The overflow CSS shorthand property sets the desired behavior when content does not fit in the
+    element's padding box (overflows) in the horizontal and/or vertical direction.
+    */
+    overflow: visible !important;
+}

docs/source/index.rst

@@ -46,14 +46,12 @@ Current checks in Macaron
 The table below shows the current set of actionable checks derived from
 the requirements that are currently supported by Macaron.
 
-.. note:: The current checks are designed based on `SLSA v0.1 <https://slsa.dev/spec/v0.1/>`_. Support for `SLSA v1.0 <https://slsa.dev/spec/v1.0/>`_ is currently under development.
-
 .. list-table:: Mapping SLSA requirements to Macaron checks
    :widths: 20 40 40
    :header-rows: 1
 
    * - SLSA level
-     - SLSA spec v0.1
+     - SLSA requirement
      - Concrete check
    * - 1
      - **Scripted build** - All build steps were fully defined in a “build script”.

docs/source/pages/checks/slsa_builds.rst

@@ -10,7 +10,7 @@ SLSA Build Levels
 SLSA Build Levels report on various security aspects of a project, to provide a score that represents its overall trustworthiness and completeness.
 See `SLSA Levels <https://slsa.dev/spec/v1.0/levels>`_.
 
-Macaron's ``Provenance verified`` check uses the criteria of SLSA Build Levels to output a result that matches the correct level for a given artifact.
+Macaron's :class:`Provenance verified <macaron.slsa_analyzer.checks.provenance_verified_check.ProvenanceVerifiedCheck>` check uses the criteria of SLSA Build Levels to output a result that matches the correct level for a given artifact.
 
 - Build Level 0: There is no provenance for the artifact.
 - Build Level 1: There is provenance for the artifact but it cannot be verified.

docs/source/pages/cli_usage/command_analyze.rst

@@ -11,7 +11,7 @@ Analyze
 Description
 -----------
 
-Analyze a public GitHub repository (and optionally the repositories of its dependencies) to determine its SLSA posture. We currently support `SLSA v0.1 <https://slsa.dev/spec/v0.1/>`_. The support for `SLSA v1.0 <https://slsa.dev/spec/v1.0/>`_ will be added in future.
+Analyze a public GitHub repository (and optionally the repositories of its dependencies) to determine its :term:`SLSA` posture.
 
 -----
 Usage