# Using the Panther detections repo

This page describes the methods you can use to leverage Panther-managed detections in the [panther-analysis](https://github.com/panther-labs/panther-analysis) repository within your [CI/CD workflow](https://docs.panther.com/~/changes/15ann7vKLltCCAGHtdQr/panther-developer-workflows/ci-cd). 

For general information and best practices for Panther detections, and for information on using web application-based workflows to manage your detections directly in the Panther Console, see the [Detections documentation](https://docs.panther.com/~/changes/15ann7vKLltCCAGHtdQr/detections).

## Methods for leveraging Panther-managed detections

There are two methods you can use to create a copy of Panther-managed detections from the panther-analysis repository:

* [A public fork ](https://docs.panther.com/~/changes/15ann7vKLltCCAGHtdQr/panther-developer-workflows/ci-cd/detections-repo/public-fork)
  * When you use a public fork, your detection content will be publicly visible.  
  * A public fork can be used to create Pull Requests to bring new detection content to the [panther-analysis upstream repo](https://github.com/panther-labs/panther-analysis).
* [A private cloned repository](https://docs.panther.com/~/changes/15ann7vKLltCCAGHtdQr/panther-developer-workflows/ci-cd/detections-repo/private-cloned-repo)
  * If you want to keep your detection content private, we recommend using a private cloned repo. With a private cloned repo, the repository settings will control who has access to the content inside the repo. 
  * Note that in this configuration, you cannot use a Pull Request to bring changes upstream.