Files
upstream-corteza/SECURITY.md
upstream-mirror 7e385fc126
Some checks failed
SonarQube / SonarQube (push) Failing after 5m28s
E2e test on main branch push / server and client test (map[name:admin port:8080]) (push) Failing after 3m33s
Server and lib tests / Library test (js) (push) Failing after 1m36s
Server and lib tests / Library test (vue) (push) Successful in 2m24s
Server and lib tests / Web client test (admin) (push) Successful in 2m52s
Server and lib tests / Web client test (compose) (push) Successful in 3m23s
Server and lib tests / Web client test (discovery) (push) Successful in 2m49s
Server and lib tests / Web client test (one) (push) Successful in 2m52s
Server and lib tests / Web client test (privacy) (push) Successful in 2m44s
Server and lib tests / Web client test (reporter) (push) Successful in 2m56s
Server and lib tests / Web client test (workflow) (push) Successful in 3m0s
Server and lib tests / Server tests (push) Failing after 4m55s
E2e test on main branch push / notify-failure (push) Failing after 9s
Server and lib tests / Send matrix testing notification (push) Successful in 2s
Mark stale issues and pull requests / stale (push) Successful in 40s
snapshot of https://github.com/cortezaproject/corteza.git (2024.9.x, 2026-09-18; blobs > 131072B omitted)
2026-09-18 01:22:23 +05:00

1.5 KiB

Security

At Corteza, the security of our products and services is important to us. All of our source code repositories are managed through GitHub organisations. Here is the list of Corteza Repositories

If you believe you have found a security vulnerability in any Corteza repository, please report it to us as described below.

Reporting Security Issues

Please do not report security vulnerabilities through public GitHub issues.

Instead, please send email to info@cortezaproject.org.

You should receive a response within 24 business hours. If for some reason you do not, please follow up via email to ensure we received your original message.

Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:

  • Type of issue,
  • full paths of source file(s) related to the manifestation of the issue,
  • the location of the affected source code (tag/branch/commit or direct URL),
  • any special configuration required to reproduce the issue,
  • step-by-step instructions to reproduce the issue,
  • proof-of-concept or exploit code (if possible),
  • impact of the issue, including how an attacker might exploit the issue.

This information will help us triage your report more quickly.

Preferred Languages

We prefer all communications to be in English.

Policy

Corteza Privacy Policy