Add files via upload

Author: DefinetlyNotAI

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[email protected].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.

CONTRIBUTING.md

@@ -0,0 +1,125 @@
+# Contributing to Logicytics
+
+Looking to contribute something to Logicytics? **Here's how you can help.**
+
+Please take a moment to review this document in order to make the contribution
+process easy and effective for everyone involved.
+
+Following these guidelines helps to communicate that you respect the time of
+the developers managing and developing this open source project. In return,
+they should reciprocate that respect in addressing your issue or assessing
+patches and features.
+
+
+## Using the issue tracker
+
+The [issue tracker](https://github.com/DefinetlyNotAI/Logicytics/issues) is
+the preferred channel for [bug reports](#bug-reports), [features requests](#feature-requests)
+and [submitting pull requests](#pull-requests), but please respect the following
+restrictions:
+
+- Please **do not** derail or troll issues. Keep the discussion on topic and
+  respect the opinions of others.
+
+- Please **do not** post comments consisting solely of "+1" or " 👍 ".
+  Use [GitHub's "reactions" feature](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)
+  instead. We reserve the right to delete comments which violate this rule.
+
+
+## Issues assignment
+
+I will be looking at the open issues, analyze them, and provide guidance on how to proceed. **Issues can be assigned to anyone other than me** However, contributors are welcome to participate in the discussion and provide their input on how to best solve the issue, and even submit a PR if they want to. Please wait that the issue is ready to be worked on before submitting a PR, we don't want to waste your time.
+
+Please keep in mind that I am small, have limited resources and am not always able to respond immediately. I will try to provide feedback as soon as possible, but please be patient. If you don't get a response immediately, it doesn't mean that we are ignoring you or that we don't care about your issue or PR. We will get back to you as soon as we can.
+
+If you decide to pull a PR or fork the project, keep in mind that you should only add/edit the scripts you need to, leave the Explain.md file and the updating of the structure file to me.
+
+## Issues and labels
+
+Our bug tracker utilizes several labels to help organize and identify issues.
+
+For a complete look at our labels, see the [project labels page](https://github.com/DefinetlyNotAI/Logicytics/labels).
+
+
+## Bug reports
+
+A bug is a _demonstrable problem_ that is caused by the code in the repository.
+Good bug reports are extremely helpful, so thanks!
+
+Guidelines for bug reports:
+
+1. **Use the GitHub issue search** — check if the issue has already been
+   reported.
+
+2. **Check if the issue has been fixed** — try to reproduce it using the
+   latest `main` (or `version` branch if the issue is about a version) in the repository.
+
+
+A good bug report shouldn't leave others needing to chase you up for more
+information. Please try to be as detailed as possible in your report. What is
+your environment? What steps will reproduce the issue? What browser(s) and OS
+experience the problem? Do other browsers show the bug differently? What
+would you expect to be the outcome? All these details will help people to fix
+any potential bugs.
+
+
+## Feature requests
+
+Feature requests are welcome. But take a moment to find out whether your idea
+fits with the scope and aims of the project. It's up to _you_ to make a strong
+case to convince the project's developers of the merits of this feature. Please
+provide as much detail and context as possible.
+
+
+## Coding Standards
+
+- **Code Style**: Follow the project's existing code style.
+
+- **Commit Messages**: Write clear and descriptive commit messages. Use the imperative mood (e.g., "Add feature" instead of "Added feature").
+- **Documentation**: Update documentation as necessary to reflect any changes you make.
+
+
+## Pull requests
+
+Good pull requests—patches, improvements, new features—are a fantastic
+help. They should remain focused in scope and avoid containing unrelated
+commits.
+
+**Please ask first** before embarking on any **significant** pull request (e.g.
+implementing features, refactoring code, porting to a different language),
+otherwise you risk spending a lot of time working on something that the
+project's developers might not want to merge into the project. For trivial
+things, or things that don't require a lot of your time, you can go ahead and
+make a PR.
+
+Please adhere to the coding guidelines used throughout the
+project (indentation, accurate comments, etc.) and any other requirements
+(such as test coverage).
+
+1. **Fork the Repository**: Fork our repository to your GitHub account.
+2. **Create a Branch**: Create a new branch for your feature or bug fix.
+3. **Make Changes**: Make your changes in the new branch.
+4. **Commit Changes**: Commit your changes with a clear and descriptive message.
+5. **Push Changes**: Push your changes to your forked repository.
+6. **Open a Pull Request**: Open a pull request on our repository. Include a detailed description of your changes and how they address the issue or implement the feature.
+
+**IMPORTANT**: By submitting a patch, you agree to allow the project owners to
+license your work under the terms of the [MIT License](https://github.com/DefinetlyNotAI/Logicytics/blob/main/LICENSE) (if it
+includes code changes) and under the terms of the
+[Creative Commons Attribution 3.0 Unported License](https://creativecommons.org/licenses/by/3.0/).
+
+
+## License
+
+By contributing your code, you agree to license your contribution under the [MIT License](https://github.com/DefinetlyNotAI/Logicytics/blob/main/LICENSE).
+By contributing to the documentation, you agree to license your contribution under the [Creative Commons Attribution 3.0 Unported License](https://creativecommons.org/licenses/by/3.0/).
+
+
+## Communication
+
+- **Issues**: Use GitHub issues for bug reports and feature requests. Keep the discussion focused and relevant.
+- **Pull Requests**: Use pull requests to propose changes. Be prepared to discuss your changes and address any feedback.
+
+If you have any questions or need further clarification, please feel free to contact us at [email protected].
+
+Thank you for your contributions!

Credit.md

@@ -0,0 +1,66 @@
+# CREDITS
+
+This project is built on the shoulders of giants and inspired by the work of many talented individuals and organizations. We acknowledge their contributions and are grateful for the knowledge and tools they have shared.
+
+
+## Bootstrap by twbs
+
+We are grateful for the work provided by Bootstrap, a popular open-source toolkit for developing responsive, mobile-first projects on the web. Bootstrap's comprehensive documentation has been valuable in shaping our project contributing.md and Issue Templates.
+
+- [Bootstrap GitHub Repository](https://github.com/twbs/bootstrap)
+
+
+## winPEAS-ng by peas
+
+We are grateful for the foundational work provided by winPEAS, a perfect open-source tool for scanning dynamic window systems in a responsive, colorful manner. winPEAS's comprehensive documentation has been invaluable in helping indirectly shape our project by allowing escalation and post-exploitation actions.
+
+- [winPEAS-ng GitHub Repository](https://github.com/peass-ng)
+
+
+## evil3ad for Collect-MemoryDump
+
+We would like to extend our sincere thanks to evil3ad for the development and incorporation of Collect-MemoryDump into our main project. This tool has been instrumental in automating the process of memory dump collection, significantly improving our efficiency and effectiveness in forensic investigations.
+
+- [Collect-MemoryDump GitHub Repository](https://github.com/evild3ad/Collect-MemoryDump)
+
+
+## Magnet Forensics
+
+Magnet Forensics has been a crucial dependency for our tool, providing essential functionalities that have enriched our abilities. We are grateful for the following tools from Magnet Forensics that have been integrated into our workflow:
+
+- [MAGNET DumpIt for Windows](https://www.magnetforensics.com/resources/magnet-dumpit-for-windows/)
+- [MAGNET Encrypted Disk Detector](https://www.magnetforensics.com/resources/encrypted-disk-detector/)
+- [MAGNET RAM Capture](https://www.magnetforensics.com/resources/magnet-ram-capture/)
+- [MAGNET Response](https://www.magnetforensics.com/resources/magnet-response/)
+
+
+## BelkaSoft's Live RAM Capturer
+
+We also acknowledge the support from BelkaSoft's Live RAM Capturer, which has been a valuable dependency for our tool, Collect-MemoryDump. This tool has played a significant role in enhancing our ability to capture live memory data, contributing to the overall success of our project.
+
+- [BelkaSoft's Live RAM Capturer](https://belkasoft.com/get)
+
+
+## Ebolaman
+
+We acknowledge the following repositories by ebolaman for their valuable contributions to our understanding and development of various tools and techniques:
+
+- [SessionSploit](https://www.youtube.com/@ebolaman_)
+- [UAC-Bypass](https://www.youtube.com/@ebolaman_)
+
+## Kurogai
+
+We are indebted to kurogai for the following repositories, which have significantly contributed to our knowledge and the development of our project:
+
+- [100-redteam-projects](https://github.com/kurogai/100-redteam-projects)
+  - Password HashCracker
+
+## Microsoft
+
+We appreciate Microsoft and their contributors for SysInternal, which has significantly contributed to the development of our project by their SysInternal Project:
+
+- [SysInternal](https://learn.microsoft.com/en-us/sysinternals/)
+
+# Acknowledgments
+
+This project would not be possible without the contributions and inspirations from the above-mentioned individuals and organizations. We are deeply grateful for their work and the community that supports it.

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Maybe Ai?
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.