Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature] "GUAC Scorecard" for artifacts/packages #1508

Open
pxp928 opened this issue Nov 16, 2023 · 0 comments
Open

[feature] "GUAC Scorecard" for artifacts/packages #1508

pxp928 opened this issue Nov 16, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@pxp928
Copy link
Collaborator

pxp928 commented Nov 16, 2023

Is your feature request related to a problem? Please describe.

With the new experimental REST interfaces being proposed, and based on some discussion around being able to get value out of GUAC while waiting for ingestion to complete (due to the lack of data from users, or that the process of ingestion of large amounts of data taking a while), we want to enable some use cases which will provide value to users that will provide instant value upon setup of GUAC and iteratively get better when more and more data gets ingested.

We discussed several options including:

  • Do i have an SBOM, If so where does that SBOM live?
  • What is my most widely used dependency
  • Top level package “Scorecard” (for ossf scorecards, licenses, etc.)

This issue describes the third option.

Describe the solution you'd like

The third option can be thought of as having a "scorecard" of what we know and don't know for a specific package.

As SBOMs and other metadata are ingested into GUAC, we want to be able to get a good idea of what information we are missing for a specific package and if that needs to be remediated.

This can include:

  1. Is there a SLSA attestation associated with the package?
  2. Is there scorecard information associated with the package source?
  3. are packages that we know nothing about (no SBOM, slsa attestation...etc)?
  4. a package that includes a high number of vulnerable dependencies

The output should be a table/list with the packages to pay attention to as well as a list of problems that they have that are actionable (missing SBOMs or SLSA attestations). This list can then be used by a security operator or developer to triage.

Describe alternatives you've considered

Other alternatives to have issues opened up for:

@pxp928 pxp928 added the enhancement New feature or request label Nov 16, 2023
@pxp928 pxp928 changed the title [feature] FILL THIS IN [feature] "Scorecard" of internally build artifacts/packages Nov 16, 2023
@pxp928 pxp928 changed the title [feature] "Scorecard" of internally build artifacts/packages [feature] "GUAC Scorecard" for artifacts/packages Nov 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant