Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Develop #10

Merged
merged 11 commits into from
Dec 13, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
43 changes: 42 additions & 1 deletion .releaserc
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,48 @@
],
"plugins": [
"@semantic-release/commit-analyzer",
"@semantic-release/release-notes-generator",
[
"@semantic-release/release-notes-generator",
{
"preset": "conventionalcommits",
"presetConfig": {
"types": [
{
"type": "feat",
"section": "Features"
},
{
"type": "fix",
"section": "Bug Fixes"
},
{
"type": "chore",
"section": "Miscellaneous Chores"
},
{
"type": "docs",
"section": "Documentation"
},
{
"type": "style",
"hidden": true
},
{
"type": "refactor",
"hidden": true
},
{
"type": "perf",
"hidden": true
},
{
"type": "test",
"hidden": true
}
]
}
}
],
"@semantic-release/npm",
"@semantic-release/github"
]
Expand Down
File renamed without changes.
48 changes: 48 additions & 0 deletions SECURITY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,48 @@
# Security Policy

## Supported Versions

The following versions of JS Validator are currently being supported with security updates:

| Version | Supported |
| ------- | ------------------ |
| 1.4.4 | :white_check_mark: |
| < 1.4.4 | :x: |

## Reporting a Vulnerability

The safety and security of JS Validator is a top priority. If you believe you have found a security vulnerability in any version of JS Validator, please follow these steps to report it:

1. **Do Not Post It Publicly**: Please do not post vulnerabilities publicly on forums, social media, or other platforms. We want to mitigate any potential harm to users by keeping the issue confidential until a fix is available.

2. **Email Your Report**: Send an email to the security team at `[email protected]`. Include a detailed report of the vulnerability, including the affected version, potential impact, and any steps to reproduce it. If possible, provide suggestions for how the vulnerability can be mitigated or fixed.

3. **Wait for Response**: Our security team will review your report and respond as quickly as possible. We appreciate your patience as we work to confirm and address the vulnerability.

4. **Disclosure Timing**: Please allow us a reasonable amount of time to fix the issue before any public disclosure. We aim to handle all security reports with the utmost urgency and care.

5. **Acknowledgment**: Contributors who report a valid security vulnerability will be acknowledged in the project's release notes, once the issue has been resolved. If you wish to remain anonymous, please let us know in your report.

## Security Patch Process

Upon receiving a security vulnerability report, our team will:

1. Confirm the vulnerability and determine its severity.
2. Develop a security patch or workaround.
3. Test the patch to ensure it effectively resolves the vulnerability without introducing new issues.
4. Release an updated version of JS Validator with the patch.
5. Publicly disclose the details of the vulnerability and its fix, acknowledging the reporter (unless anonymity is requested).

## Security Best Practices for Users

- **Stay Updated**: Always use the latest version of JS Validator. Older versions may contain security vulnerabilities that have been fixed in newer releases.
- **Review Validation Rules**: Regularly review your validation rules and configurations to ensure they meet your current security requirements.
- **Monitor for Updates**: Keep an eye on the project repository and update notifications to stay informed about new releases and security patches.

## Contact Information

For any security concerns or inquiries, please contact `[email protected]`.

---

This security policy is subject to change. Please refer to the latest version in the project repository for current guidelines and procedures. Your contributions in keeping JS Validator secure are greatly appreciated.
13 changes: 13 additions & 0 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

1 change: 1 addition & 0 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,7 @@
"@types/jest": "^29.5.10",
"@typescript-eslint/eslint-plugin": "^6.13.1",
"@typescript-eslint/parser": "^6.13.1",
"conventional-changelog-conventionalcommits": "^7.0.2",
"eslint": "^8.54.0",
"jest": "^29.7.0",
"semantic-release": "^22.0.12",
Expand Down
Loading