Comparing version 1.1.1 to 1.1.2
{ | ||
"name": "jsonverse", | ||
"version": "1.1.1", | ||
"version": "1.1.2", | ||
"description": "jsonVerse is a lightweight JSON-based database package for Node.js. It provides a simple interface to store, retrieve, and manage data using JSON files.", | ||
@@ -5,0 +5,0 @@ "main": "index.js", |
@@ -5,6 +5,33 @@ # Security Policy | ||
| Version | Supported | | ||
| ------- | ------------------ | | ||
| 1.1 | :white_check_mark: | | ||
| 1.0 | :white_check_mark: | | ||
We are currently supporting the following versions of the `jsonverse` package: | ||
- 1.0.0 to 1.0.13 | ||
- 1.1.0 to 1.1.2 | ||
## Reporting a Vulnerability | ||
If you discover a security vulnerability within the `jsonverse` package, please send an email to marco5dev@example.com. All security vulnerabilities will be promptly addressed. | ||
Please do not open GitHub issues for security vulnerabilities. | ||
## Responsible Disclosure | ||
We appreciate the security community's efforts in responsibly disclosing security vulnerabilities. We will acknowledge your efforts and work together to fix any issues promptly. | ||
## Security Updates | ||
Security updates will be released as new versions of the package. It is highly recommended that you keep your dependencies up to date by regularly checking for and applying updates. | ||
```bash | ||
npm update jsonverse | ||
``` | ||
## Code Review | ||
We take security seriously and conduct regular code reviews to identify and fix potential security vulnerabilities in our codebase. However, if you come across any security concerns or have suggestions, feel free to contact us. | ||
## Code of Conduct | ||
This project follows a [Code of Conduct](https://github.com/Marco5dev/jsonverse/blob/main/CODE_OF_CONDUCT.md). We expect all contributors and users to adhere to it to ensure a safe and respectful environment for everyone. | ||
Thank you for using the `jsonverse` package. Your security is our priority. |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
25297