chore(docs): minor fixes

CODE_OF_CONDUCT.md

@@ -3,7 +3,7 @@
 ## Our Pledge
 
 In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
+contributors and maintainers pledge to make participation in our project and
 our community a harassment-free experience for everyone, regardless of age, body
 size, disability, ethnicity, sex characteristics, gender identity and expression,
 level of experience, education, socio-economic status, nationality, personal
@@ -23,13 +23,13 @@ include:
 Examples of unacceptable behavior by participants include:
 
 * The use of sexualized language or imagery and unwelcome sexual attention or
- advances
+  advances
 * Trolling, insulting/derogatory comments, and personal or political attacks
 * Public or private harassment
 * Publishing others' private information, such as a physical or electronic
- address, without explicit permission
+  address, without explicit permission
 * Other conduct which could reasonably be considered inappropriate in a
- professional setting
+  professional setting
 
 ## Our Responsibilities
 
@@ -45,25 +45,12 @@ threatening, offensive, or harmful.
 
 ## Scope
 
-This Code of Conduct applies both within project spaces and in public spaces
+This Code of Conduct applies within all project spaces, and it also applies when
-when an individual is representing the project or its community. Examples of
+an individual is representing the project or its community in public spaces.
-representing a project or community include using an official project e-mail
+Examples of representing a project or community include using an official
-address, posting via an official social media account, or acting as an appointed
+project e-mail address, posting via an official social media account, or acting
-representative at an online or offline event. Representation of a project may be
+as an appointed representative at an online or offline event. Representation of
-further defined and clarified by project maintainers.
+a project may be further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at skylot@gmail.com. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
 
 ## Attribution
 

SECURITY.md

@@ -2,6 +2,7 @@
 
 ## Reporting a Vulnerability
 
-To report a security issue, please email `skylot@gmail.com` with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue.
+To report a security issue, please open a [new security advisory](https://github.com/skylot/jadx/security/advisories/new).
-We will check and respond within 3 working days. If the issue is confirmed as a vulnerability, we will apply required mitigations at the next release.
+Please fill the steps you took to create the issue, affected versions, and, if known, mitigations for the issue.
-This project follows a 90 day disclosure timeline.
+We will check and respond within 3 working days.
+If the issue is confirmed as a vulnerability, we will apply required mitigations at the next release.

buildSrc/src/main/kotlin/jadx-library.gradle.kts

@@ -42,7 +42,7 @@ publishing {
 					developer {
 						id.set("skylot")
 						name.set("Skylot")
-						email.set("skylot@gmail.com")
+						email.set(project.properties["libEmail"].toString())
 						url.set("https://github.com/skylot")
 					}
 				}