-
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updated dependencies and fixed issue with recursively inline scripts
- Loading branch information
Showing
13 changed files
with
1,748 additions
and
4,564 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
# This workflow will run tests using node and then publish a package to GitHub Packages when a release is created | ||
# For more information see: https://docs.github.com/en/actions/publishing-packages/publishing-nodejs-packages | ||
|
||
name: Node.js Package | ||
|
||
on: | ||
release: | ||
types: [created] | ||
|
||
jobs: | ||
publish-npm: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- uses: actions/checkout@v3 | ||
- uses: actions/setup-node@v3 | ||
with: | ||
node-version: 18 | ||
registry-url: https://registry.npmjs.org/ | ||
- run: npm ci | ||
- run: npm publish | ||
env: | ||
NODE_AUTH_TOKEN: ${{secrets.npm_token}} |
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,24 @@ | ||
Security Policy | ||
=============== | ||
|
||
We value your contributions and feedback, and we want to ensure the security and | ||
reliability of our software for all users. As part of our commitment to | ||
security, we have established this security policy to help you report any | ||
vulnerabilities that you may discover. | ||
|
||
If you believe you have found a security vulnerability in our software, please | ||
let us know immediately. You may find our contact information at | ||
<https://exact.realty/.well-known/security.txt>. Please include the following | ||
information in your report: | ||
|
||
* A brief description of the vulnerability | ||
* Steps to reproduce the vulnerability | ||
* The version of our software affected by the vulnerability | ||
* Your contact information (email or other means of communication) | ||
|
||
We kindly ask that you do not disclose the vulnerability to anyone else until we | ||
have had the opportunity to investigate and address it. We will respond to your | ||
report as soon as possible and work with you to resolve the issue. We may also | ||
provide credit to you in our release notes or other public acknowledgments. | ||
|
||
Thank you for helping to keep our software secure! |
Oops, something went wrong.