@enterprise-cmcs/macpro-security-hub-sync - npm Package Compare versions

Comparing version 1.0.1 to 1.0.2

package.json

		@@ -7,3 +7,3 @@ {
		},
		"version": "1.0.1",
		"version": "1.0.2",
		"description": "NPM module to create Jira issues for all findings in Security Hub for the current AWS account..",
		@@ -53,15 +53,4 @@ "main": "./dist/index.js",
		"@semantic-release/release-notes-generator",
		"@semantic-release/changelog",
		"@semantic-release/npm",
		"@semantic-release/github",
		[
		"@semantic-release/git",
		{
		"assets": [
		"CHANGELOG.md",
		"package.json"
		],
		"message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
		}
		]
		"@semantic-release/github"
		]
		@@ -68,0 +57,0 @@ },

README.md

		@@ -31,3 +31,3 @@ <h1 align="center" style="border-bottom: none;">macpro-security-hub-sync</h1>

		- When the sync utility is run, each Security Hub Finding type (Title) is represented as a single issue. So if you have violated the 'S3.8' rule three individual times, you will have one S3.8 GH Issue created.
		- When the sync utility is run, each Security Hub Finding type (Title) is represented as a single issue. So if you have violated the 'S3.8' rule three individual times, you will have one S3.8 Jira Issue created.
		- By default, CRITICAL and HIGH severity findings get issues created in Jira. However, this is configurable in either direction (more or less sensitivity).
		@@ -34,0 +34,0 @@ - When the utility runs, previously created Jira issues that no longer have an active finding are closed. In this way, Jira issues can be automatically closed as the Findings are resolved, if you run the utility on a schedule (recommended).

New alerts