0f0a534f25
Some checks failed
CI Pipeline / Rust Format Check (push) Successful in 6s
CI Pipeline / Clippy Lints (push) Successful in 53s
CI Pipeline / Rust Unit Tests (push) Failing after 1m11s
CI Pipeline / Security Audit (push) Successful in 4s
CI Pipeline / Frontend Lint & Type Check (push) Successful in 15s
CI Pipeline / Build .deb & Release (push) Has been skipped
47 lines
1.5 KiB
Markdown
47 lines
1.5 KiB
Markdown
# Security Policy
|
|
|
|
## Supported Versions
|
|
|
|
Only the **latest release** is currently supported with security updates.
|
|
|
|
| Version | Supported |
|
|
|---------|----------|
|
|
| Latest | ✅ |
|
|
| Older | ❌ |
|
|
|
|
## Reporting a Vulnerability
|
|
|
|
**Do not report security vulnerabilities through public GitHub Issues.**
|
|
|
|
Instead, use GitHub's private vulnerability reporting:
|
|
|
|
👉 [Report a vulnerability for Linux-Patch-Manager](https://github.com/Draco-Lunaris/Linux-Patch-Manager/security/advisories/new)
|
|
|
|
This allows us to coordinate a fix before public disclosure.
|
|
|
|
### Response Timeline
|
|
|
|
- **Acknowledgment** within 48 hours
|
|
- **Initial assessment** within 7 days
|
|
- **Ongoing updates** on remediation progress
|
|
|
|
## Disclosure Policy
|
|
|
|
We follow **coordinated disclosure**:
|
|
|
|
- We ask for **90 days** before public disclosure of a vulnerability
|
|
- Security advisories are published via [GitHub Security Advisories](https://github.com/Draco-Lunaris/Linux-Patch-Manager/security/advisories)
|
|
- We will work with you to determine an appropriate disclosure timeline when a fix requires more time
|
|
|
|
## Security Best Practices
|
|
|
|
This project is a security tool — we hold ourselves to a high standard:
|
|
|
|
- **Signed commits**: All commits must be signed (SSH signing)
|
|
- **CI enforcement**: All PRs require passing CI checks (fmt, clippy, test, audit, build)
|
|
- **Dependency auditing**: `cargo audit` runs in CI to catch known vulnerabilities
|
|
|
|
## Credit
|
|
|
|
Contributors who responsibly report vulnerabilities will be credited in the corresponding GitHub Security Advisory.
|