POST: How to exchange data between tools in the software supply chain

Open
#22 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript

Research direction

The issue proposes a post for the Docusaurus/markdown-based aboutcode.org repository. Start by reviewing the site's existing post structure, then research the listed SBOM, package-manifest, registry, VEX, and vulnerability-data formats. The topic and the desired path forward need agreement before completion can be defined.

Written by the indexing model from the issue text.

Description

blog

How to exchange data between tools in the software supply chain?

Let's review the current (sad) state of affairs and plot a path forward. Can SBOMs save the day and find their killer app?

We will check SPDX, CycloneDX, PURL, Kissbom, custom formats, and all the menagerie of package manifests and lockfiles, various package registry APIs, VEX specs, and vulnerability data formats like OSV and CVE.org.

Dominant language
JavaScript
Stars
9
Forks
18
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aboutcode-org/www.aboutcode.org

All issues in aboutcode-org/www.aboutcode.org

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.