├── LICENSE ├── README.md ├── CONTRIBUTING.md └── CODE_OF_CONDUCT.md /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) 2023 JP Rodriguez 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE. 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Flipper Zero Hacking Scripts 2 | 3 | Welcome to the Flipper Zero Hacking Scripts repository! This collection of scripts is designed for ethical hacking and educational purposes, specifically tailored for use with Flipper Zero devices. 4 | 5 | ## Disclaimer 6 | 7 | These scripts are intended for responsible and legal use. Unauthorized or malicious activities are strictly prohibited. By using these scripts, you agree to be bound by the terms of the included license. 8 | 9 | ## Features 10 | 11 | - Script 1: [Brief description] 12 | - Script 2: [Brief description] 13 | - ... 14 | 15 | ## Getting Started 16 | 17 | ### Prerequisites 18 | 19 | - A flipper zero device is required. 20 | - Most scripts are written for MACOS 21 | 22 | ### Installation 23 | 24 | 1. [Step-by-step installation instructions] 25 | 26 | ### Usage 27 | 28 | 1. [How to use each script] 29 | 2. ... 30 | 31 | ## Contributing 32 | 33 | We welcome contributions! If you have improvements or additional scripts to share, please follow our [contribution guidelines](CONTRIBUTING.md). 34 | 35 | ## License 36 | 37 | This project is licensed under the [Your Chosen License] - see the [LICENSE](LICENSE) file for details. 38 | 39 | ## Acknowledgments 40 | 41 | - [Credits or acknowledgments, if any] 42 | 43 | ## Community Guidelines 44 | 45 | Please adhere to our [community guidelines](CONTRIBUTING.md) to maintain a positive and ethical environment. 46 | 47 | ## Contact 48 | 49 | If you have any questions or concerns, feel free to reach out to [Your Contact Information]. 50 | 51 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contributing to Flipper Zero Hacking Scripts 2 | 3 | Thank you for considering contributing to this project! Your contributions help improve and grow the Flipper Zero Hacking Scripts community. 4 | 5 | ## Code of Conduct 6 | 7 | Please note that this project is released with a [Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project, you agree to abide by its terms. 8 | 9 | ## How to Contribute 10 | 11 | We welcome contributions in the form of bug reports, feature requests, documentation improvements, and code contributions. 12 | 13 | ### Reporting Bugs 14 | 15 | If you find a bug, please open a new issue, providing details such as: 16 | 17 | - A clear and concise description of the bug. 18 | - Steps to reproduce the issue. 19 | - Expected behavior. 20 | - Screenshots or code snippets, if applicable. 21 | 22 | ### Feature Requests 23 | 24 | If you have an idea for a new feature, please open a new issue and include: 25 | 26 | - A clear and concise description of the feature. 27 | - The problem it solves or the improvement it brings. 28 | 29 | ### Code Contributions 30 | 31 | If you'd like to contribute code: 32 | 33 | 1. Fork the repository. 34 | 2. Create a new branch for your feature or bug fix: `git checkout -b feature/new-feature` or `git checkout -b bugfix/fix-issue`. 35 | 3. Make your changes and commit them with clear messages. 36 | 4. Push your branch to your fork: `git push origin feature/new-feature`. 37 | 5. Submit a pull request to the `main` branch of the main repository. 38 | 39 | Please ensure your code follows the existing style and conventions. Include tests for new features or fixes. 40 | 41 | ### Documentation 42 | 43 | Improvements to the documentation are always welcome! If you find typos, missing information, or have suggestions for better explanations, please submit a pull request. 44 | 45 | ## Code Style 46 | 47 | Please follow the existing code style and conventions used in the project. 48 | 49 | ## Licensing 50 | 51 | By contributing to this project, you agree that your contributions will be licensed under the project's [license](LICENSE). 52 | 53 | ## Contact 54 | 55 | If you have any questions or need further clarification, feel free to contact us at [Your Contact Information]. 56 | 57 | Happy hacking! 58 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Flipper Zero Hacking Scripts Code of Conduct 2 | 3 | ## Our Pledge 4 | 5 | We, as contributors and maintainers, pledge to make participation in our project and community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation. 6 | 7 | ## Our Standards 8 | 9 | Examples of behavior that contributes to creating a positive environment include: 10 | 11 | - Using welcoming and inclusive language 12 | - Being respectful of differing viewpoints and experiences 13 | - Gracefully accepting constructive criticism 14 | - Focusing on what is best for the community 15 | - Showing empathy towards other community members 16 | 17 | Examples of unacceptable behavior by participants include: 18 | 19 | - The use of sexualized language or imagery and unwelcome sexual attention or advances 20 | - Trolling, insulting/derogatory comments, and personal or political attacks 21 | - Public or private harassment 22 | - Publishing others' private information, such as a physical or electronic address, without explicit permission 23 | - Other conduct that could reasonably be considered inappropriate in a professional setting 24 | 25 | ## Responsibilities of Contributors 26 | 27 | Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. 28 | 29 | Contributors to the project are expected to adhere to the Code of Conduct in all project spaces, including project repositories, issue trackers, chat channels, and social media. 30 | 31 | ## Enforcement 32 | 33 | Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [Your Contact Information]. The project team will review and investigate all complaints and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. 34 | 35 | ## Attribution 36 | 37 | This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 2.0, available at [https://www.contributor-covenant.org/version/2/0/code_of_conduct.html](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html). 38 | 39 | For answers to common questions about this code of conduct, see [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). 40 | 41 | heisenpwn@proton.me 42 | --------------------------------------------------------------------------------