├── .github
└── workflows
│ ├── codeql-analysis.yml
│ ├── contributors.yml
│ └── go.yml
├── .gitignore
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── CONTRIBUTORS.svg
├── LICENSE
├── README.md
├── assets
├── bugcrowd.svg
├── facebook.svg
├── github.svg
├── hackerone.svg
├── home.svg
├── instagram.svg
├── intigriti.svg
├── medium.svg
├── reddit.svg
├── stackoverflow.svg
├── twitter.svg
├── yeswehack.svg
└── youtube.svg
├── data
├── D0rkerDevil.toml
├── Ice3man543.toml
├── Jhaddix.toml
├── README.md
├── Random_Robbie.toml
├── aemsecurity.toml
├── alra3ees.toml
├── brutelogic.toml
├── bsysop.toml
├── burpbounty.toml
├── edoardottt.toml
├── hahwul.toml
├── hakluke.toml
├── hussein98d.toml
├── insiderphd.toml
├── kathanp19.toml
├── nahamsec.toml
├── orange_8361.toml
├── pry0cc.toml
├── s0md3v.toml
├── stokfredrik.toml
├── thedawgyg.toml
├── todayisnew.toml
├── tomnomnom.toml
├── wagiro.toml
└── xelkomy.toml
├── distribute.go
├── go.mod
├── go.sum
└── template
├── foot.md
└── head.md
/.github/workflows/codeql-analysis.yml:
--------------------------------------------------------------------------------
1 | # For most projects, this workflow file will not need changing; you simply need
2 | # to commit it to your repository.
3 | #
4 | # You may wish to alter this file to override the set of languages analyzed,
5 | # or to provide custom queries or build logic.
6 | #
7 | # ******** NOTE ********
8 | # We have attempted to detect the languages in your repository. Please check
9 | # the `language` matrix defined below to confirm you have the correct set of
10 | # supported CodeQL languages.
11 | #
12 | name: "CodeQL"
13 |
14 | on:
15 | push:
16 | branches: [ main ]
17 | pull_request:
18 | # The branches below must be a subset of the branches above
19 | branches: [ main ]
20 | schedule:
21 | - cron: '19 23 * * 2'
22 |
23 | jobs:
24 | analyze:
25 | name: Analyze
26 | runs-on: ubuntu-latest
27 |
28 | strategy:
29 | fail-fast: false
30 | matrix:
31 | language: [ 'go' ]
32 | # CodeQL supports [ 'cpp', 'csharp', 'go', 'java', 'javascript', 'python' ]
33 | # Learn more:
34 | # https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#changing-the-languages-that-are-analyzed
35 |
36 | steps:
37 | - name: Checkout repository
38 | uses: actions/checkout@v2
39 |
40 | # Initializes the CodeQL tools for scanning.
41 | - name: Initialize CodeQL
42 | uses: github/codeql-action/init@v1
43 | with:
44 | languages: ${{ matrix.language }}
45 | # If you wish to specify custom queries, you can do so here or in a config file.
46 | # By default, queries listed here will override any specified in a config file.
47 | # Prefix the list here with "+" to use these queries and those in the config file.
48 | # queries: ./path/to/local/query, your-org/your-repo/queries@main
49 |
50 | # Autobuild attempts to build any compiled languages (C/C++, C#, or Java).
51 | # If this step fails, then you should remove it and run the build manually (see below)
52 | - name: Autobuild
53 | uses: github/codeql-action/autobuild@v1
54 |
55 | # ℹ️ Command-line programs to run using the OS shell.
56 | # 📚 https://git.io/JvXDl
57 |
58 | # ✏️ If the Autobuild fails above, remove it and uncomment the following three lines
59 | # and modify them (or add more) to build your code if your project
60 | # uses a compiled language
61 |
62 | #- run: |
63 | # make bootstrap
64 | # make release
65 |
66 | - name: Perform CodeQL Analysis
67 | uses: github/codeql-action/analyze@v1
68 |
--------------------------------------------------------------------------------
/.github/workflows/contributors.yml:
--------------------------------------------------------------------------------
1 | name: Contributors
2 | on:
3 | schedule:
4 | - cron: '0 1 * * 0' # At 01:00 on Sunday.
5 | push:
6 | workflow_dispatch:
7 | inputs:
8 | logLevel:
9 | description: 'manual run'
10 | required: false
11 | default: ''
12 | jobs:
13 | contributors:
14 | runs-on: ubuntu-latest
15 | steps:
16 | - uses: bubkoo/contributors-list@v1
17 | with:
18 | GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
19 | svgPath: CONTRIBUTORS.svg
20 |
--------------------------------------------------------------------------------
/.github/workflows/go.yml:
--------------------------------------------------------------------------------
1 | name: Distribute
2 |
3 | on:
4 | push:
5 | workflow_dispatch:
6 | inputs:
7 | logLevel:
8 | description: 'Log level'
9 | required: true
10 | default: 'warning'
11 | tags:
12 | description: 'Test scenario tags'
13 |
14 | jobs:
15 |
16 | build:
17 | runs-on: ubuntu-latest
18 | steps:
19 | - uses: actions/checkout@v2
20 |
21 | - name: Set up Go
22 | uses: actions/setup-go@v2
23 | with:
24 | go-version: 1.15
25 |
26 | - name: Build
27 | run: go build -o distribute -v ./...
28 |
29 | - name: Running Distribute
30 | run: ./distribute
31 |
32 | - name: Commit files
33 | run: |
34 | git config --local user.email "hahwul@gmail.com"
35 | git config --local user.name "MemBi"
36 | git add README.md
37 | git commit -m "Changed readme"
38 | - name: Push changes
39 | uses: ad-m/github-push-action@master
40 | with:
41 | github_token: ${{ secrets.GITHUB_TOKEN }}
42 | branch: ${{ github.ref }}
43 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | # Binaries for programs and plugins
2 | *.exe
3 | *.exe~
4 | *.dll
5 | *.so
6 | *.dylib
7 |
8 | # Test binary, built with `go test -c`
9 | *.test
10 |
11 | # Output of the go coverage tool, specifically when used with LiteIDE
12 | *.out
13 |
14 | # Dependency directories (remove the comment below to include it)
15 | # vendor/
16 |
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Contributor Covenant Code of Conduct
2 |
3 | ## Our Pledge
4 |
5 | In the interest of fostering an open and welcoming environment, we as
6 | contributors and maintainers pledge to making participation in our project and
7 | our community a harassment-free experience for everyone, regardless of age, body
8 | size, disability, ethnicity, sex characteristics, gender identity and expression,
9 | level of experience, education, socio-economic status, nationality, personal
10 | appearance, race, religion, or sexual identity and orientation.
11 |
12 | ## Our Standards
13 |
14 | Examples of behavior that contributes to creating a positive environment
15 | include:
16 |
17 | * Using welcoming and inclusive language
18 | * Being respectful of differing viewpoints and experiences
19 | * Gracefully accepting constructive criticism
20 | * Focusing on what is best for the community
21 | * Showing empathy towards other community members
22 |
23 | Examples of unacceptable behavior by participants include:
24 |
25 | * The use of sexualized language or imagery and unwelcome sexual attention or
26 | advances
27 | * Trolling, insulting/derogatory comments, and personal or political attacks
28 | * Public or private harassment
29 | * Publishing others' private information, such as a physical or electronic
30 | address, without explicit permission
31 | * Other conduct which could reasonably be considered inappropriate in a
32 | professional setting
33 |
34 | ## Our Responsibilities
35 |
36 | Project maintainers are responsible for clarifying the standards of acceptable
37 | behavior and are expected to take appropriate and fair corrective action in
38 | response to any instances of unacceptable behavior.
39 |
40 | Project maintainers have the right and responsibility to remove, edit, or
41 | reject comments, commits, code, wiki edits, issues, and other contributions
42 | that are not aligned to this Code of Conduct, or to ban temporarily or
43 | permanently any contributor for other behaviors that they deem inappropriate,
44 | threatening, offensive, or harmful.
45 |
46 | ## Scope
47 |
48 | This Code of Conduct applies both within project spaces and in public spaces
49 | when an individual is representing the project or its community. Examples of
50 | representing a project or community include using an official project e-mail
51 | address, posting via an official social media account, or acting as an appointed
52 | representative at an online or offline event. Representation of a project may be
53 | further defined and clarified by project maintainers.
54 |
55 | ## Enforcement
56 |
57 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
58 | reported by contacting the project team at hahwul@gmail.com. All
59 | complaints will be reviewed and investigated and will result in a response that
60 | is deemed necessary and appropriate to the circumstances. The project team is
61 | obligated to maintain confidentiality with regard to the reporter of an incident.
62 | Further details of specific enforcement policies may be posted separately.
63 |
64 | Project maintainers who do not follow or enforce the Code of Conduct in good
65 | faith may face temporary or permanent repercussions as determined by other
66 | members of the project's leadership.
67 |
68 | ## Attribution
69 |
70 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71 | available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72 |
73 | [homepage]: https://www.contributor-covenant.org
74 |
75 | For answers to common questions about this code of conduct, see
76 | https://www.contributor-covenant.org/faq
77 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | ## Add/Change new user data
2 | 1. First fork this repo.
3 | 2. Clone forked repo
4 | ```
5 | $ git clone https://github.com/${your-username}/MemBi
6 | $ cd MemBi
7 | ```
8 | 3. See format of toml https://github.com/hahwul/MemBi/blob/main/data/README.md
9 | 4. Add or Change user data in `./data/*.toml`
10 | + e.g (hahwul.toml)
11 | ```toml
12 | name = "hahuwl"
13 | site = "https://www.hahwul.com"
14 | hackerone = "hahwul"
15 | bugcrowd = "hahwul"
16 | twitter = "hahwul"
17 | github = "hahwul"
18 | instagram = "hahwul___"
19 | youtube = "https://youtube.com/c/하훌"
20 | stackoverflow = "11547708/hahwul"
21 | ```
22 | 5. git push
23 | ```
24 | $ git add ./data/*.toml ; git commit -m "change toml data" ; git push
25 | ```
26 | 6. Make and Send Pull-Request for master repo
27 |
28 | ## Note
29 | `./distribute` lets you reflect it in README. However, this operation is performed automatically when pushing through Github-action.
30 |
31 | * Q. I want to see the readme. What if I want to do this? 🤔
32 | * A. 🚀
33 | ```
34 | $ go build distribute.go
35 | $ ./distribute
36 | ```
37 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | MIT License
2 |
3 | Copyright (c) 2021 HAHWUL
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 |
2 |
3 |
4 |
5 | Member of Bugbounty and Infosec
6 |
7 |
8 |
9 |
10 |
11 |
2 |
3 |
4 |
5 | Member of Bugbounty and Infosec
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 | ## 🤔 What is MemBi?
14 | MemBi is all the members of bugbounty and infosec project.
15 | If you don't know who to follow, see!
16 |
17 | ## 🌏 Contribute
18 | 
19 |
20 | If you want to contribute to this project, please check the document below! In fact, it's simple, just fork this repo and add a toml file to the `/data/` subpath and push, create a pull-request.
21 |
22 | [CONTRIBUTING.md](/CONTRIBUTING.md) / [TOML Keys](/data/README.md)
23 |
24 | ## 🌟 Members
25 |
--------------------------------------------------------------------------------
4 | 
8 | 
9 | 
10 | 
11 |