-
-
Notifications
You must be signed in to change notification settings - Fork 28.1k
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
Add AI in Cybersecurity #3129
base: main
Are you sure you want to change the base?
Add AI in Cybersecurity #3129
Conversation
f0658c5
to
993cee4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @ElNiak,
Some things I noticed:
Includes the Awesome badge - Should be placed on the right side of the readme heading.
The awesome badge is included but not at the specified location currently.
Has a Table of Contents section. - Should be named Contents
Your table of contents isn't named.
Has a table of contents - Should only have one level of nested lists, preferably none.
Your table of contents has 3 levels
Has a table of contents - Must not feature
Contributing
orFootnotes
sections.
Your table of contents does include a contributing section. You should use contributing.md
for this instead.
Has an appropriate license - A code license like MIT, BSD, Apache, GPL, etc, is not acceptable
Your repo has an MIT license which is deemed inappropriate.
Has consistent formatting and proper spelling/grammar. - The link and description are separated by a dash. Example:
- [AVA](…) - JavaScript test runner.
This is one of the major strange things I found with your repo. You quite often repeat the name with a link, which feels unnecessary to me e.g. * DeepExploit - [DeepExploit](...)\r\n * <Description>
. This seems unnecessarily different to all other awesome repos.
Does not include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.
And your awesome list does explicitly include one of these.
Making the description shorter with less unnecessary text would be nicer and easier for the user. 😄 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The URL to your list should end in #readme
.
@@ -677,6 +677,7 @@ | |||
- [Suricata](https://github.com/satta/awesome-suricata#readme) - Intrusion detection/prevention system and network security monitoring engine. | |||
- [Prompt Injection](https://github.com/FonduAI/awesome-prompt-injection#readme) - A type of vulnerability that specifically targets machine learning models. | |||
- [Detection Engineering](https://github.com/infosecB/awesome-detection-engineering#readme) - Design, build, and operate detective cybersecurity controls. | |||
- [AI in Cybersecurity](https://github.com/ElNiak/awesome-ai-cybersecurity) - AI applications in cybersecurity and how to secure AI used in applications. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- [AI in Cybersecurity](https://github.com/ElNiak/awesome-ai-cybersecurity) - AI applications in cybersecurity and how to secure AI used in applications. | |
- [AI in Cybersecurity](https://github.com/ElNiak/awesome-ai-cybersecurity#readme) - AI applications in cybersecurity and how to secure AI used in applications. |
https://github.com/ElNiak/awesome-ai-cybersecurity
Aims to provide an organized collection of high-quality resources on AI applied to Cybersecurity (using AI and protecting AI) to help professionals. Should be here since AI and cybersecurity are among the most promising field in computer science.
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions. Comments pointing out lint violation are allowed, but does not count as a review.
Add Name of List
. It should not contain the wordAwesome
.Add Swift
Add Software Architecture
Update readme.md
Add Awesome Swift
Add swift
add Swift
Adding Swift
Added Swift
- [iOS](…) - Mobile operating system for Apple phones and tablets.
- [Framer](…) - Prototyping interactive UI designs.
- [iOS](…) - Resources and tools for iOS development.
- [Framer](…)
- [Framer](…) - prototyping interactive UI designs
#readme
.- [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.
Requirements for your Awesome list
That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
awesome-lint
on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.main
, notmaster
.Mobile operating system for Apple phones and tablets.
Prototyping interactive UI designs.
Resources and tools for iOS development.
Awesome Framer packages and tools.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
awesome-name-of-list
.awesome-swift
awesome-web-typography
awesome-Swift
AwesomeWebTypography
# Awesome Name of List
.# Awesome Swift
# Awesome Web Typography
# awesome-swift
# AwesomeSwift
awesome-list
&awesome
as GitHub topics. I encourage you to add more relevant topics.Awesome X
and a logo withAwesome X
. You can put the header image in a#
(Markdown header) or<h1>
.Contents
, notTable of Contents
.Contributing
orFootnotes
sections.https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0
(replace<user>
and<repo>
accordingly).license
orLICENSE
in the repo root with the license text.Licence
section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.unicorn
.contributing.md
. The casing is up to you.Contributing
, positioned at the top or bottom of the main content.Footnotes
section at the bottom of the readme. The section should not be present in the Table of Contents.Example:
- [AVA](…) - JavaScript test runner.
Node.js
, notNodeJS
ornode.js
.You can still use a CI for linting, but the badge has no value in the readme.
Inspired by awesome-foo
orInspired by the Awesome project
kinda link at the top of the readme. The Awesome badge is enough.Go to the top and read it again.