Skip to content

Commit b3ec6ac

Browse files
committed
Update docs
1 parent f96044f commit b3ec6ac

File tree

2 files changed

+29
-2
lines changed

2 files changed

+29
-2
lines changed

README.md

+3-2
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
# CodeIgniter Website
22

3-
[![](https://github.com/lonnieezell/ci-website/workflows/PHPUnit/badge.svg)](https://github.com/lonnieezell/ci-website/actions?query=workflow%3A%22PHPUnit%22)
4-
[![](https://github.com/lonnieezell/ci-website/workflows/PHPStan/badge.svg)](https://github.com/lonnieezell/ci-website/actions?query=workflow%3A%PHPStan%22)
3+
[![](https://github.com/lonnieezell/ci-website/workflows/PHPUnit/badge.svg)](https://github.com/lonnieezell/ci-website/actions/workflows/test.yml)
4+
[![](https://github.com/lonnieezell/ci-website/workflows/PHPStan/badge.svg)](https://github.com/lonnieezell/ci-website/actions/workflows/analyze.yml)
5+
[![](https://github.com/lonnieezell/ci-website/workflows/Deptrac/badge.svg)](https://github.com/lonnieezell/ci-website/actions/workflows/inspect.yml)
56
[![Coverage Status](https://coveralls.io/repos/github/lonnieezell/ci-website/badge.svg?branch=develop)](https://coveralls.io/github/lonnieezell/ci-website?branch=develop)
67

78
This is the official website for the CodeIgniter PHP framework.

SECURITY.md

+26
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
# Security Policy
2+
3+
The development team and community take all security issues seriously. **Please do not make public any uncovered flaws.**
4+
5+
## Reporting a Vulnerability
6+
7+
Thank you for improving the security of our code! Any assistance in removing security flaws will be acknowledged.
8+
9+
**Please report security flaws by emailing the development team directly: [email protected]**.
10+
11+
The lead maintainer will acknowledge your email within 48 hours, and will send a more detailed response within 48 hours indicating
12+
the next steps in handling your report. After the initial reply to your report, the security team will endeavor to keep you informed of the
13+
progress towards a fix and full announcement, and may ask for additional information or guidance.
14+
15+
## Disclosure Policy
16+
17+
When the security team receives a security bug report, they will assign it to a primary handler.
18+
This person will coordinate the fix and release process, involving the following steps:
19+
20+
- Confirm the problem and determine the affected versions.
21+
- Audit code to find any potential similar problems.
22+
- Prepare fixes for all releases still under maintenance. These fixes will be released as fast as possible.
23+
24+
## Comments on this Policy
25+
26+
If you have suggestions on how this process could be improved please submit a Pull Request.

0 commit comments

Comments
 (0)