Update

README.md

@@ -7,14 +7,12 @@
 ![GitHub License](https://img.shields.io/github/license/th3maid/witch_craft)
 ![GitHub top language](https://img.shields.io/github/languages/top/th3maid/witch_craft)
 
-<center>
-  <br>
-    <h1>WITCH_CRAFT</h1>
-  <br>
-</center>
+<p align="center">
+  <h1>WITCH_CRAFT</h1>
+</p>
 
 <p align="center">
-  🎉 Welcome to the WITCH_CRAFT Community!
+  🎉 Welcome to the witch_craft Community!
 </p>
 
 ---
@@ -29,7 +27,7 @@ https://cosmic-zip.github.io/wiki/wiki.html
 
 ### Plugins
 
-The Witch_Craft project is extensible through static files and Rust code. Moreover, it is possible to extend its functionalities using `db.json`. This file contains a list of small shell scripts, which means you can integrate anything that interacts with the terminal using ARGS (argsv, readargs(), sys.args(), etc).
+The witch_craft project is extensible through static files and Rust code. Moreover, it is possible to extend its functionalities using `db.json`. This file contains a list of small shell scripts, which means you can integrate anything that interacts with the terminal using ARGS (argsv, readargs(), sys.args(), etc).
 
 **Note**: There is a Python script called sort.py inside /var/witch_craft/witch_spells/dataset. It is used to create a sorted version of the dataset.
 
@@ -132,7 +130,7 @@ witch_craft nuke.hd --device /dev/sdx1
 ```
 
 ```bash
-witch_craft search.social --ip 172.16.0.1
+witch_craft search.meta --keywork "Anonymous"
 ```
 
 ```bash

SECURITY.md

@@ -1,4 +1,4 @@
- Security Policy
+# Security Policy
 
 Although we do our best to prevent vulnerabilities, and have tools to help
 catch most of them, we are humans after all, and there will be inevitably
@@ -9,77 +9,9 @@ witch_craft suite, or in our presence online (website, forum, emails,
 DNS, etc.).
 
 Depending on which category they fall into, different information is
-needed. We
-do believe in coordinated disclosure, so in order to address them, and
+needed. We do believe in coordinated disclosure, so in order to address them, and
 coordinate disclosure with you (and properly credit you for the
-discovery),
-report them to us. Do not open bug reports or pull requests.
+discovery), report them to us. Do not open bug reports or pull requests.
 
-Our contact email for security issues is TBA
-
-If you are unsure how to proceed, need clarifications or have questions or
-remarks about this policy, feel free to email us to inquire.
-
-## witch_craft suite vulnerabilities
-
-### Supported versions
-
-We only support the latest stable present on TBA
-
-For security issues present in our GitHub repository (master or any
-recently
-active branch), open a pull request or bug report.
-
-For any security issue affecting older versions of witch_craft still
-present
-in currently supported Linux or BSD distributions, file a report with
-them,
-and email us a short description of the vulnerability along with a link to
-the bug report.
-
-### Reporting
-
-There is no particular template to report the vulnerabilities. Keep
-in mind
-that a vulnerability is essentially a bug, so please provide us detailed
-information on how to reproduce it, such as:
-
-- Which witch_craft tools are affected? And how? Any proof of concept to
-demonstrate it?
-- Operating systems involved, kernel versions (`uname -a` and
-`lsb_release -a` for example).
-- CPU architecture (`witch_craft -v` output is useful); a vulnerability
-on a
-x86 32 bit may not be exploitable on ARM 64 bit. A bug may also only
-be present
-when witch_craft is compiled a certain way.
-- All the commands needed to trigger the issue.
-- Did you compile it yourself or did you get it from a package?
-- What equipment did you use? A packet capture may be useful; different
-equipment behaves differently, they have different Wi-Fi stacks,
-drivers, and
-firmware.
-- A patch to fix the issue, if available.
-- If CVE numbers have been assigned, please provide them as well.
-
-### Public disclosure
-
-Although it is essentially a bug, do not submit a bug report or a pull
-request,
-but email us the data first, so we can coordinate fixing the issue
-and assist
-you in filing the bug reports, and if you provided a patch, the pull
-request; a
-patch may need to be broken down in multiple commits for clarity,
-for example.
-
-## Online presence
-
-For any security issue affecting us specifically (any witch_craft.org
-subdomain) such as misconfiguration of our hosting, DNS, email, servers,
-or misconfiguration of the software we are using, email us with all the
-details regarding your findings.
-
-Anything else should be reported to the author or provider of the
-software,
-hardware, or hosting.
+Bug found? Questions? Access witch_craft community:
+[discussions](https://github.com/cosmic-zip/witch_craft/discussions)