|
1 |
| -# demo |
2 |
| -Demo project with various Open Source obstacles |
| 1 | +# Debricked Demo Repository |
| 2 | + |
| 3 | +This is an intentionally vulnerable demo repository by [Debricked](https://debricked.com) that showcases common obstacles and risks related to open source dependencies. It demonstrates how our tool helps you analyze, detect, manage and remediate open source risks. |
| 4 | + |
| 5 | +## Getting Started |
| 6 | + |
| 7 | +### 1. Get a copy of the Repository |
| 8 | + |
| 9 | +> [!NOTE] |
| 10 | +>This repository comes with a pre-configured GitHub Actions workflow located at [.github/workflows/debricked.yml](.github/workflows/debricked.yml), but it is also possible to use your CI/CD tool of choice or download/clone the repository and scan it locally using the [Debricked CLI](https://github.com/debricked/cli/tree/main). For more information on integrating with other tools, visit [the documentation](https://docs.debricked.com/tools-and-integrations/integrations). |
| 11 | +
|
| 12 | +The easiest way to get set up is to simply fork or import this repository to your own GitHub account, making use of the existing GitHub Actions workflow. |
| 13 | + |
| 14 | +#### 1.1 (If forking the repository) Enable GitHub Actions in Forked Repositories |
| 15 | + |
| 16 | +If you've forked this repository, please note that GitHub disables running workflows by default. To enable them: |
| 17 | + |
| 18 | +1. Navigate to the **Actions** tab in your forked repository. |
| 19 | +2. Click the button labeled **"I understand my workflows, go ahead and enable them"**. |
| 20 | + |
| 21 | +This step is necessary for the workflows to run as expected. |
| 22 | + |
| 23 | +### 2. Configure Your Debricked Access Token |
| 24 | + |
| 25 | +To enable the dependency scans with GitHub actions, set up your Debricked Access Token as a GitHub secret: |
| 26 | + |
| 27 | +1. Generate an Access Token through the Debricked UI (instructions can be found [here](https://docs.debricked.com/product/administration/generate-access-token)) |
| 28 | +2. Navigate to the repository on GitHub. |
| 29 | +3. Go to **Settings** > **Secrets and variables** > **Actions**. |
| 30 | +4. Click **New repository secret**. |
| 31 | +5. Name the secret `DEBRICKED_API_KEY` and paste your Access Token as the value. |
| 32 | + |
| 33 | +### 3. Run a scan |
| 34 | + |
| 35 | +Once the API key is configured, the workflow will automatically scan your repository for dependency issues on: |
| 36 | +* Every push to any branch. |
| 37 | +* [Manually triggering the workflow](https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/manually-running-a-workflow#running-a-workflow) |
| 38 | + |
| 39 | +## Repository Structure |
| 40 | + |
| 41 | +- **[.github/workflows/debricked.yml](.github/workflows/debricked.yml)**: |
| 42 | + Contains the GitHub Actions workflow that triggers the Debricked dependency scan. |
| 43 | +- **[README.md](README.md)**: |
| 44 | + This documentation file. |
| 45 | +- **[LICENSE](LICENSE)**: |
| 46 | + The repository license. |
| 47 | +- **[web/](web/)**: |
| 48 | + Folder with code related to the frontend, using various vulnerable open source dependencies |
| 49 | +- **[src/](src/)**: |
| 50 | + Folder with code related to the backend, which is set up using a vulnerable version of the [Spring Framework](https://spring.io/projects/spring-framework). |
| 51 | + |
| 52 | +## Additional Resources |
| 53 | + |
| 54 | +- [Debricked Website](https://debricked.com) |
| 55 | +- [Debricked Documentation](https://docs.debricked.com) |
| 56 | +- [GitHub Actions Documentation](https://docs.github.com/en/actions) |
| 57 | + |
| 58 | +## Contributing |
| 59 | + |
| 60 | +Contributions to improve this demo are welcome! Please open an issue or submit a pull request with your suggestions. |
| 61 | + |
| 62 | +## License |
| 63 | + |
| 64 | +This repository is licensed under the MIT License. See the [LICENSE](LICENSE) file for more details. |
0 commit comments