# Define a Security-Oriented CI Environment

A robust CI/CD pipeline is essential for Solidity development, ensuring code quality, security, and streamlined deployments. Below are the key components and tools to incorporate into your pipeline.

***

## 1. Continuous Integration Platforms

* [**GitHub Actions**](https://github.com/features/actions)
* [**GitLab CI/CD**](https://docs.gitlab.com/ee/ci/)
* [**CircleCI**](https://circleci.com/)
* [**Travis CI**](https://travis-ci.com/)

## 2. Test Coverage Tools

* [**solidity-coverage**](https://github.com/sc-forks/solidity-coverage)**:** A Hardhat plugin that measures test coverage for Solidity projects.
* [**Forge Coverage**](https://book.getfoundry.sh/)**:** A feature within Foundry for generating test coverage reports, ideal for Rust-based Solidity workflows.

## 3. Testing Frameworks

* [**Hardhat**](https://hardhat.org/)**:** A flexible development environment for compiling, deploying, and testing smart contracts.
* [**Foundry**](https://book.getfoundry.sh/)**:** A Rust-based framework with powerful testing features, including fuzz testing and gas profiling.

## 4. Security and Static Analysis Tools

* [**Slither**](https://github.com/crytic/slither)**:** A static analysis tool for detecting vulnerabilities and enforcing best practices.
* [**MythX**](https://mythx.io/)**:** A cloud-based smart contract security scanner offering detailed vulnerability reports.
* [**Echidna**](https://github.com/crytic/echidna)**:** A fuzzer for testing invariants and edge cases in Ethereum smart contracts.

## 5. Code Quality and Style Enforcement

* [**Solhint**](https://protofire.github.io/solhint/)**:** A linter for Solidity that enforces coding standards and best practices.
* [**Prettier Plugin for Solidity**](https://github.com/prettier-solidity/prettier-plugin-solidity)**:** Ensures consistent formatting of Solidity code, automating style checks within pipelines.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.optimumsec.xyz/coding/security-oriented-ci.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.