PowerShell / PowerShell/DSC

Support SBOMs for resources

Open
#540 1 comment 0 reactions 1 assignee View on GitHub

@theJasonHelmick is already working on this.

Since Oct 16, 2024.

Issue-Enhancement Needs Triage Partner-MC
Dominant language
Rust
Stars
523
Forks
75
Avg merge
3d 16h
Merged PRs (30d)
24

Description

Summary of the new feature / enhancement

As an infrastructure engineer, I want to be able to review a software bill of materials (SBOM) for a resource before I use it in my production environment, so I can comply with regulations/policies and have increased confidence in the provenance of the software that modifies my systems.

Proposed technical implementation details (optional)

Ideally, we should be able to have a manifest at least point to an SBOM that describes the commands the manifest uses. Potentially, we could reuse the path discovery mechanism to look for SBOMs by convention relative to the manifest file.

I can think of a few potential further integrations, but at least being able to associate the SBOM with the resource seems like a first step.

Contributor guide

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.