Thank you for your interest in contributing to projects maintained by Biswadeb Mukherjee's Lab. Contributions from the community help improve research quality, tooling reliability, and the overall security ecosystem.
This document outlines the process and expectations for contributing to repositories within this organisation.
Contributions are welcome in several areas, including:
- bug fixes and stability improvements
- documentation improvements
- feature enhancements
- performance optimizations
- research contributions and experimental modules
All contributions should align with the organization's focus on offensive security research, malware engineering, reconnaissance, and security tooling.
- Fork the repository you wish to contribute to.
- Create a new branch for your changes.
git checkout -b feature/your-feature-name- Make your changes and ensure the code builds and functions correctly.
- Commit your changes with clear and descriptive messages.
- Push your branch to your fork.
- Open a Pull Request against the main repository.
To maintain consistency across projects, contributors should follow these general guidelines:
- Write clear, maintainable, and well-structured code.
- Follow the conventions of the programming language used in the repository.
- Include comments where necessary to explain complex logic.
- Avoid unnecessary dependencies.
- Ensure the project builds and runs correctly after your changes.
Where applicable, please include the following header in source files:
SPDX-License-Identifier: MIT
Use clear and concise commit messages that describe the purpose of the change.
Examples:
fix: resolve memory leak in scanner module
feat: add new OSINT data source integration
docs: improve installation instructions
refactor: simplify payload loader logic
Good documentation is essential. Contributions that improve the following are highly appreciated:
- installation instructions
- usage examples
- architecture explanations
- research notes
This organization publishes tools and research related to offensive security. Contributions should:
- focus on research, education, or authorised testing
- Avoid including harmful payloads intended for real-world misuse
- maintain responsible disclosure practices when discussing vulnerabilities
If your contribution involves sensitive security research, please contact the maintainer before submitting a public pull request.
By contributing to any repository within this organisation, you agree that your contributions will be released under the same license used by the repository, unless otherwise specified.
All contributions are subject to review by the project maintainer. Contributions that do not follow the guidelines described in this document may be rejected.
The maintainers reserve the right to:
- reject pull requests that violate project guidelines
- close issues that do not follow repository rules or scope
- decline contributions that may introduce legal, security, or ethical concerns
These measures help maintain the integrity, quality, and research focus of the organisation’s projects.
Mr. Biswadeb Mukherjee
Offensive Security Researcher & Malware Engineer
Website https://official-biswadeb941.in