Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions SECURITY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
# Security Policy

## Supported Versions

Use this section to tell people about which versions of your project are
currently being supported with security updates.
Comment on lines +5 to +6

Choose a reason for hiding this comment

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

medium

This section contains placeholder text from the default GitHub security policy template. Please remove this instructional text, as the section header and table are self-explanatory.


| Version | Supported |
| ------- | ------------------ |
| 5.1.x | :white_check_mark: |
| 5.0.x | :x: |
| 4.0.x | :white_check_mark: |
| < 4.0 | :x: |
Comment on lines +10 to +13

Choose a reason for hiding this comment

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

medium

The versions listed in the support table appear to be examples. Please update this table with the actual versions of your project and their current security support status.


## Reporting a Vulnerability

Use this section to tell people how to report a vulnerability.

Tell them where to go, how often they can expect to get an update on a
reported vulnerability, what to expect if the vulnerability is accepted or
declined, etc.
Comment on lines +17 to +21

Choose a reason for hiding this comment

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

high

This section contains placeholder text for reporting vulnerabilities. It's crucial to replace this with a clear and specific process. You should detail how to report a vulnerability (e.g., via email to a specific address, or using GitHub's private vulnerability reporting feature), expected response times, and what the reporter can expect from the process.

Suggested change
Use this section to tell people how to report a vulnerability.
Tell them where to go, how often they can expect to get an update on a
reported vulnerability, what to expect if the vulnerability is accepted or
declined, etc.
We take all security bugs in this project seriously. If you believe you have found a security vulnerability, please report it to us through one of the following channels:
- **Email**: Send an email to `security@example.com`.
- **GitHub Private Vulnerability Reporting**: Use the [private vulnerability reporting feature](https://github.com/FirebaseExtended/firebase-framework-tools/security/advisories/new) on this repository.
You can expect a response from us within 48 hours. If the issue is confirmed, we will release a patch as soon as possible depending on complexity.