github.com/phillinzzz/newBsc@v1.1.6/SECURITY.md (about)

     1  # Security Policy
     2  
     3  ## Supported Versions
     4  
     5  Please see [Releases](https://github.com/binance-chain/bsc/releases). We recommend using the [most recently released version](https://github.com/binance-chain/bsc/releases/latest).
     6  
     7  ## Audit reports
     8  
     9  Audit reports are published in the `docs` folder: https://github.com/binance-chain/bsc/tree/master/docs/audits 
    10  
    11  | Scope | Date | Report Link |
    12  | ------- | ------- | ----------- |
    13  | `geth` | 20170425 | [pdf](https://github.com/phillinzzz/newBsc/blob/master/docs/audits/2017-04-25_Geth-audit_Truesec.pdf) |
    14  | `clef` | 20180914 | [pdf](https://github.com/phillinzzz/newBsc/blob/master/docs/audits/2018-09-14_Clef-audit_NCC.pdf) |
    15  
    16  ## Reporting a Vulnerability
    17  
    18  **Please do not file a public ticket** mentioning the vulnerability.
    19  
    20  To find out how to disclose a vulnerability in Ethereum visit [https://bugcrowd.com/binance](https://bugcrowd.com/binance) or email bounty@ethereum.org. Please read the [disclosure page](https://github.com/binance-chain/bsc/security/advisories) for more information about publicly disclosed security vulnerabilities.
    21  
    22  Use the built-in `geth version-check` feature to check whether the software is affected by any known vulnerability. This command will fetch the latest [`vulnerabilities.json`](https://geth.ethereum.org/docs/vulnerabilities/vulnerabilities.json) file which contains known security vulnerabilities concerning `geth`, and cross-check the data against its own version number.