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 9 times, most recently from 772fbde to abf5004 Compare January 27, 2026 09:27
@thomasschafer thomasschafer marked this pull request as ready for review January 27, 2026 10:30
@thomasschafer thomasschafer requested review from a team as code owners January 27, 2026 10:30
@thomasschafer thomasschafer force-pushed the feat/add-uv-support-to-snyk-sbom branch 2 times, most recently from b97a18e to cbef593 Compare January 27, 2026 11:35
@thomasschafer thomasschafer force-pushed the feat/add-uv-support-to-snyk-sbom branch from cbef593 to eef6ff6 Compare January 27, 2026 13:38
.send(`{"errors":[{"title":"Bad Request","detail":"invalid SBOM"}]}`);
}

if (req.params.orgId === '55555555-5555-5555-5555-555555555555') {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: In your tests you can set the response instead of hardcoding it in the fakeserver, for example take a look at setEndpointResponse()

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah I didn't know that was possible - done

SNYK_API: 'http://localhost:' + port + baseApi,
SNYK_HOST: 'http://localhost:' + port,
SNYK_TOKEN: '123456789',
SNYK_DISABLE_ANALYTICS: '1',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: Ensure to set SNYK_HTTP_PROTOCOL_UPGRADE=0 to avoid issues.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done!

Copy link
Contributor

@PeterSchafer PeterSchafer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving with minor improvement suggestions.

@thomasschafer thomasschafer force-pushed the feat/add-uv-support-to-snyk-sbom branch 6 times, most recently from 3a09f2d to 1d0af42 Compare January 29, 2026 12:38
@thomasschafer thomasschafer force-pushed the feat/add-uv-support-to-snyk-sbom branch from 1d0af42 to e82c7a0 Compare January 29, 2026 14:33
@thomasschafer thomasschafer merged commit acb804c into main Jan 29, 2026
6 checks passed
@thomasschafer thomasschafer deleted the feat/add-uv-support-to-snyk-sbom branch January 29, 2026 17:19
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.

5 participants