Skip to content

Commit 9be1f35

Browse files
Add security policy
1 parent 89e02fa commit 9be1f35

File tree

1 file changed

+34
-0
lines changed

1 file changed

+34
-0
lines changed

SECURITY.md

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
# Security Policy
2+
3+
## Supported Versions
4+
5+
We release patches for security vulnerabilities in the latest major version of the package:
6+
7+
| Version | Supported |
8+
| ------- | ------------------ |
9+
| Latest | :white_check_mark: |
10+
| Older | :x: |
11+
12+
## Reporting a Vulnerability
13+
14+
If you discover a security vulnerability, please report it to us as follows:
15+
16+
1. **Email us**: Send an email to [security@swimlane.com](mailto:security@swimlane.com) with the details of the vulnerability.
17+
2. **Provide details**: Include as much information as possible about the vulnerability, including steps to reproduce it, potential impact, and any suggested fixes.
18+
3. **Wait for a response**: We will acknowledge your email within 72 hours and provide a timeline for a fix.
19+
20+
## Security Updates
21+
22+
We will release security updates as needed. Users are encouraged to update to the latest version to ensure they have the latest security fixes.
23+
24+
## Security Best Practices
25+
26+
To help secure your Angular project, we recommend the following best practices:
27+
28+
- **Keep dependencies up to date**: Regularly update your project dependencies to the latest versions.
29+
- **Use HTTPS**: Ensure your application is served over HTTPS to protect data in transit.
30+
- **Sanitize inputs**: Always sanitize user inputs to prevent injection attacks.
31+
- **Enable Content Security Policy (CSP)**: Use CSP to mitigate cross-site scripting (XSS) and other code injection attacks.
32+
- **Regularly review code**: Conduct regular code reviews to identify and fix potential security issues.
33+
34+
Thank you for helping us keep our project secure!

0 commit comments

Comments
 (0)