Skip to content

Conversation

@thomasschafer
Copy link
Contributor

@thomasschafer thomasschafer commented Jan 22, 2026

Pull Request Submission Checklist

  • Follows CONTRIBUTING guidelines
  • Commit messages
    are release-note ready, emphasizing
    what was changed, not how.
  • Includes detailed description of changes
  • Contains risk assessment (Low | Medium | High) - n/a
  • Highlights breaking API changes (if applicable) - n/a
  • Links to automated tests covering new functionality
  • Includes manual testing instructions (if necessary)
  • Updates relevant GitBook documentation (PR link: ___) - n/a
  • Includes product update to be announced in the next stable release notes - n/a

What does this PR do?

This PR adds uv support to snyk sbom. Note that this feature is not yet in Closed Beta, and requires a feature flag to be enabled.

How should this be manually tested?

Turn on the enableUvCLI feature flag, and then build the CLI on this branch. Then run <path/to/local/cli> sbom, optionally with --all-projects. If there is a uv.lock present, you should see an SBOM generated as expected for that uv project.

What's the product update that needs to be communicated to CLI users?

None

@thomasschafer thomasschafer force-pushed the feat/add-uv-support-to-snyk-sbom branch 7 times, most recently from 6831df7 to 0c999d7 Compare January 23, 2026 16:55
@thomasschafer thomasschafer force-pushed the feat/add-uv-support-to-snyk-sbom branch from 0c999d7 to 772fbde Compare January 23, 2026 21:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants