Huang Xin
0e516f6e56
Add ~290 new unit tests covering utils (lru, diff, css, a11y, walk, usage, txt-worker), services (EdgeTTSClient, transformers), and suppress noisy console output across all test files. Rename 27 camelCase test files to dash-case for consistency. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
38 lines
1.3 KiB
Markdown
38 lines
1.3 KiB
Markdown
# Security Policy
|
|
|
|
## Supported Versions
|
|
|
|
Readest does not currently maintain separate release channels. Security updates are provided only for the latest release series.
|
|
|
|
| Version | Supported |
|
|
| ------- | ------------------ |
|
|
| 0.10.x | :white_check_mark: |
|
|
| < 0.10 | :x: |
|
|
|
|
## Reporting a Vulnerability
|
|
|
|
Please report suspected vulnerabilities privately. Do not open a public GitHub
|
|
issue or discussion for security-sensitive reports.
|
|
|
|
Use GitHub's private vulnerability reporting for this repository:
|
|
|
|
<https://github.com/readest/readest/security/advisories/new>
|
|
|
|
When submitting a report, include:
|
|
|
|
- A clear description of the issue and the affected component
|
|
- Steps to reproduce, proof of concept, or a minimal test case
|
|
- The versions, platforms, or environments you tested
|
|
- Any suggested remediation or mitigating details, if available
|
|
|
|
What to expect after you report:
|
|
|
|
- We will aim to acknowledge receipt within 3 business days.
|
|
- We may contact you for additional details, reproduction steps, or validation.
|
|
- If the report is accepted, we will work on a fix and coordinate disclosure.
|
|
- If the report is declined, we will explain why, for example if the behavior is
|
|
expected, unsupported, or not reproducible.
|
|
|
|
Please keep vulnerability details private until a fix is available and the
|
|
maintainers have approved disclosure.
|