-
-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
b20daeb
commit 69e19c7
Showing
7 changed files
with
68 additions
and
25 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
Binary file not shown.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
## NEXTGENCSS | ||
## Version 0.1 | ||
## v0.1 Release (Not Stable) | ||
|
||
|
||
Next step | ||
|
||
We are happy to announce that , now we have made more classes and and utilities. | ||
|
||
The v0.1 (Not Stable) version will have : | ||
- Curve border classes | ||
- Some templates for copy paste | ||
- Navbar Component | ||
# NOTE:- The documentation for v0.1 is not updated yet , we will update it as fast as possible (5-1-2024) | ||
|
||
# Happy New year Happy coding !!. | ||
|
||
|
||
If you want to contribute or help us or suggest any improvement | ||
E - mail : aarti19830@gmail.com | ||
Github : |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
## Security Policy | ||
|
||
Thank you for your interest in NextGenCSS! We take security seriously and are committed to providing a secure product for our users. | ||
|
||
This document outlines our security policy and how we address security vulnerabilities. | ||
|
||
### Reporting Security Vulnerabilities | ||
|
||
If you believe you have discovered a security vulnerability in NextGenCSS, please report it to us responsibly. You can report vulnerabilities by emailing us at [email protected] | ||
|
||
Please include the following information in your report: | ||
|
||
* A description of the vulnerability | ||
* Steps to reproduce the vulnerability | ||
* Any potential impact of the vulnerability | ||
|
||
We will investigate all reported vulnerabilities and take appropriate action to address them. We will also work with you to keep your report confidential. | ||
|
||
### Security Best Practices | ||
|
||
In addition to reporting vulnerabilities, we encourage you to follow these security best practices when using NextGenCSS: | ||
|
||
* Use the latest version of NextGenCSS. | ||
* Keep your dependencies up to date. | ||
* Avoid using third-party libraries with known vulnerabilities. | ||
* Use strong passwords and keep them confidential. | ||
* Be careful when sharing sensitive information. | ||
|
||
By following these best practices, you can help to keep your applications secure. | ||
|
||
### Security Audits | ||
|
||
We regularly conduct security audits of NextGenCSS to identify and address potential vulnerabilities. We also welcome third-party security audits. | ||
|
||
### Conclusion | ||
|
||
We are committed to providing a secure product for our users. We appreciate your help in keeping NextGenCSS secure. | ||
|
||
Thank you for using NextGenCSS! | ||
|
||
Please note that this is a general security policy and may not be exhaustive. We may update this policy at any time. |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.