Skip to content
/ broker Public

A broker system between a public service and a private service

License

Notifications You must be signed in to change notification settings

snyk/broker

Folders and files

NameName
Last commit message
Last commit date
Apr 25, 2025
Jan 17, 2024
Sep 15, 2023
Feb 18, 2025
Apr 24, 2025
Apr 24, 2025
Apr 25, 2025
Apr 15, 2025
Apr 24, 2025
Oct 26, 2023
Jul 15, 2020
Feb 7, 2024
Feb 29, 2024
Jun 30, 2020
Feb 5, 2024
Sep 5, 2024
Jul 15, 2020
Nov 5, 2024
Apr 24, 2025
Aug 11, 2016
Jun 1, 2023
Feb 12, 2025
Aug 27, 2024
Feb 8, 2024
Feb 17, 2025
Mar 20, 2025
Mar 1, 2025
Nov 7, 2024
May 14, 2024
Sep 25, 2024
Apr 8, 2025
Apr 8, 2025
Feb 7, 2024
Mar 5, 2024
Jun 5, 2024
Aug 29, 2024
Aug 29, 2024
Oct 10, 2024
Mar 1, 2025
Apr 8, 2025
Mar 1, 2024
Feb 5, 2024
Nov 7, 2019
Apr 2, 2025
Apr 2, 2025
Feb 11, 2025

Repository files navigation

Snyk logo

Known Vulnerabilities


snyk/broker

Snyk Broker proxies access between snyk.io and your Git repositories, such as GitHub Enterprise, GitHub.com and Bitbucket Server. Snyk Broker can also be used to enable a secure connection with your on-premise Jira deployment.

The Broker server and client establish an applicative tunnel, proxying requests from snyk.io to the Git (fetching manifest files from monitored repositories), and vice versa (webhooks posted by the Git).

The Broker client runs within the user's internal network, keeping sensitive data such as Git tokens within the network perimeter. The applicative tunnel scans and adds only relevant requests to an approved list, narrowing down the access permissions to the bare minimum required for Snyk to actively monitor a repository.

More details here

Usage

Please refer to our extensive documentation.