Skip to content

Commit 4d2d544

Browse files
mickmickshclaude
andcommitted
add private vulnerability disclosure channel via GitHub PVRT
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1 parent b809d55 commit 4d2d544

3 files changed

Lines changed: 55 additions & 0 deletions

File tree

.github/ISSUE_TEMPLATE/config.yml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,3 +9,6 @@ contact_links:
99
- name: npm Package
1010
url: https://www.npmjs.com/package/@lap-platform/lapsh
1111
about: Check the latest published version on npm
12+
- name: Security Vulnerability
13+
url: https://github.com/Lap-Platform/lap/security/advisories/new
14+
about: Report a security vulnerability privately (do not open a public issue)

CONTRIBUTING.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -37,6 +37,10 @@ Open a GitHub issue with:
3737
- What happened instead
3838
- Minimal reproduction steps
3939

40+
## Security Issues
41+
42+
If you discover a security vulnerability, **do not open a public issue**. See [SECURITY.md](SECURITY.md) for how to report it privately.
43+
4044
## License
4145

4246
By contributing, you agree that your contributions will be licensed under the Apache License 2.0.

SECURITY.md

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
# Security Policy
2+
3+
## Supported Versions
4+
5+
| Version | Supported |
6+
|---------|-----------|
7+
| 0.6.x | Yes |
8+
| < 0.6 | No |
9+
10+
Only the latest release receives security fixes. We recommend always running the most recent version.
11+
12+
## Reporting a Vulnerability
13+
14+
**Do not open a public GitHub issue for security vulnerabilities.**
15+
16+
Instead, use GitHub's private vulnerability reporting:
17+
18+
1. Go to the [Security tab](https://github.com/Lap-Platform/lap/security) of this repository
19+
2. Click **"Report a vulnerability"**
20+
3. Fill in the advisory form
21+
22+
### What to include
23+
24+
- Description of the vulnerability
25+
- Steps to reproduce
26+
- Affected versions
27+
- Impact assessment (what an attacker could do)
28+
- Any suggested fix, if you have one
29+
30+
### What to expect
31+
32+
- **Acknowledgment** -- within 3 business days
33+
- **Initial assessment** -- within 7 business days
34+
- **Fix timeline** -- depends on severity, but we aim for 30 days for critical issues
35+
36+
We will coordinate with you on disclosure timing. We ask that you do not publicly disclose the vulnerability until a fix is released.
37+
38+
## Out of Scope
39+
40+
The following are not considered security vulnerabilities:
41+
42+
- Spec compilation accuracy or output differences -- use a [bug report](https://github.com/Lap-Platform/lap/issues/new?template=bug-report.yml)
43+
- Denial of service via extremely large input files (LAP is a local CLI tool)
44+
- Issues in dependencies -- report those upstream, but let us know if they affect LAP
45+
46+
## Credit
47+
48+
We appreciate responsible disclosure and will credit reporters in the release notes (unless you prefer to remain anonymous).

0 commit comments

Comments
 (0)