Security Policy

This is our policy for reporting security vulnerabilities and overall guidelines on what you should do upon discovering one.

Note

This document also outlines the measures we have put in to prevent security vulnerabilities in the first place.

---

Reporting Security Vulnerabilities

Please report security advistiry from "New draft security advisory" in the Security tab

In order to report a security vulnerability, you can use GitHub's built-in tool which easily allows you to calculate an attack vector/CVSS string or attribute to an existing CVE code. This allows the FluentHub Team to accurately calculate the severity and/or importance of preventing it.

Spotting secrets in code

If you spot a secret in the code, please let us know by contacting us on Discord via private DM. This helps us quietly remove the vulnerability without letting others abuse it. If you notice that we've accidentally published an AppCredentials.config file or removed it from the .gitignore in the project root, please notify us.

GitHub API

FluentHub relies heavily on the GitHub GraphQL and legacy REST API. If you believe that you have found a security vulnerability in the API and not FluentHub, please please please report it on via bounty.github.com, GitHub's official site for reporting vulnerabilities. This helps keep all open-source code safe and protects millions of developers, governments and other organisations across the world.

All bounty submissions are rated by GitHub using a purposefully simple scale.

Our Measures

What have we done to keep FluentHub safe?

Dependabot

We have implemented Dependabot alerts to automatically track security vulnerabilities that apply to the repository's dependencies.

Code scanning

We have enabled GitHub Code Scanning to automatically scan our code for potential GitHub client secrets and other API tokens.

Security advisories

We have enabled GitHub security advisories to let us know if a potential security problem might affect our repository or if something doesn't look right with any of our other security vulnerability countermeasures. This makes it easy to track potential errors or problems that might expose user credentials publicly or cause other similar problems.