Fortify Application Security provides your team with solutions to empower DevSecOps practices, enable cloud transformation, and secure your software supply chain. As the sole Code Security solution with over two decades of expertise and acknowledged as a market leader by all major analysts, Fortify delivers the most adaptable, precise, and scalable AppSec platform available, supporting the breadth of tech you use and integrated into your preferred toolchain. We firmly believe that your great code demands great security, and with Fortify, go beyond 'check the box' security to achieve that.
The files in this repository are meant to be used for repositories owned by OpenText Fortify. Its main purposes are as follows:
- Ensure that every repository (that utilizes shared-doc-resources) contains a standard set of documentation files, like README.md, LICENSE.txt, USAGE.md, ...
- Ensure consistent documentation contents, like having the same support statement and marketing intro in every repository.
Note that some of the standard documentation contents are duplicated between this repository and the https://github.com/fortify/.github repository, which contains default community health files and organization readme file. The shared-doc-resources and .github repositories are not automatically synchronized. When updating standard documentation contents in this repository, please make sure to apply corresponding changes to the https://github.com/fortify/.github repository.
For example, when updating templates/CODE_OF_CONDUCT.template.md in this repository, you should also update https://github.com/fortify/.github/blob/main/CODE_OF_CONDUCT.md. Similarly, when updating the marketing statement in includes/p.marketing-intro.md, you should also update the marketing statement in the organization README.md.
- Usage: USAGE.md
- Static Files: https://github.com/fortify/shared-doc-resources/tree/main/static
- Templates: https://github.com/fortify/shared-doc-resources/tree/main/templates
- Scripts: https://github.com/fortify/shared-doc-resources/tree/main/scripts
- Contributing Guidelines: CONTRIBUTING.md
- Code of Conduct: CODE_OF_CONDUCT.md
- License: LICENSE.txt
The only warranties for products and services of Open Text and its affiliates and licensors (“Open Text”) are as may be set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Open Text shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.
The software is provided "as is" and is not supported through the regular OpenText Support channels. Support requests may be submitted through the GitHub Issues page for this repository. A (free) GitHub account is required to submit new issues or to comment on existing issues.
Support requests created through the GitHub Issues page may include bug reports, enhancement requests and general usage questions. Please avoid creating duplicate issues by checking whether there is any existing issue, either open or closed, that already addresses your question, bug or enhancement request. If an issue already exists, please add a comment to provide additional details if applicable.
Support requests on the GitHub Issues page are handled on a best-effort basis; there is no guaranteed response time, no guarantee that reported bugs will be fixed, and no guarantee that enhancement requests will be implemented. If you require dedicated support for this and other Fortify software, please consider purchasing OpenText Fortify Professional Services. OpenText Fortify Professional Services can assist with general usage questions, integration of the software into your processes, and implementing customizations, bug fixes, and feature requests (subject to feasibility analysis). Please contact your OpenText Sales representative or fill in the Professional Services Contact Form to obtain more information on pricing and the services that OpenText Fortify Professional Services can provide.
This document was auto-generated from README.template.md; do not edit by hand