Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add OSINT #983

Closed
wants to merge 3 commits into from
Closed

Add OSINT #983

wants to merge 3 commits into from

Conversation

spmedia
Copy link

@spmedia spmedia commented Jun 2, 2017

Add in OSINT (open source intelligence tools and resources) to Security section.

https://github.com/jivoi/awesome-osint

A great list of resources for those in the security industry that conduct recon and OSINT around the web.

By submitting this pull request I confirm I've read and complied with the below requirements.

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

  • I have read and understood the contribution guidelines and the instructions for creating a list.
  • This pull request has a descriptive title.
    For example, Add Name of List, not Update readme.md or Add awesome list.
  • The entry in the Awesome list should:
    • Include a short description about the project/theme of the list. It should not describe the list itself.
      Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
    • Be added at the bottom of the appropriate category.
  • The list I'm submitting complies with these requirements:
    • Has been around for at least 30 days.
      That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
    • It's the result of hard work and the best I could possibly produce.
    • Non-generated Markdown file in a GitHub repo.
    • Includes a succinct description of the project/theme at the top of the readme. (Example)
    • The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
    • Not a duplicate.
    • Only has awesome items. Awesome lists are curations of the best, not everything.
    • Includes a project logo/illustration whenever possible.
      • Placed at the top-right of the readme. (Example)
      • The image should link to the project website or any relevant website.
      • The image should be high-DPI. Set it to maximum half the width of the original image.
    • Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
    • Has the Awesome badge on the right side of the list heading,
    • Has a Table of Contents section.
      • Should be named Contents, not Table of Contents.
      • Should be the first section in the list.
    • Has an appropriate license.
      • That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
      • If you use a license badge, it should be SVG, not PNG.
    • Has contribution guidelines.
      • The file should be named contributing.md. Casing is up to you.
    • Has consistent formatting and proper spelling/grammar.
      • Each link description starts with an uppercase character and ends with a period.
        Example: - [AVA](…) - JavaScript test runner.
      • Drop all the A / An prefixes in the descriptions.
      • Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
    • Doesn't include a Travis badge.
      You can still use Travis for list linting, but the badge has no value in the readme.
  • Go to the top and read it again.

Add in OSINT (open source intelligence tools and resources) to Security section.
@sindresorhus
Copy link
Owner

By submitting this pull request I confirm I've read and complied with the below requirements.

Please read it.

@sindresorhus sindresorhus changed the title Add OSINT to Security section Add OSINT Jul 22, 2017
@sindresorhus
Copy link
Owner

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.

Missing lots of description. Just a list of different services is not very useful without more context. What is it and how can it be used for OSINT.

@spmedia
Copy link
Author

spmedia commented Jul 22, 2017

Yes, I have slowly been going through the list and adding descriptions to each + removing lower quality services.

@sindresorhus
Copy link
Owner

@spmedia ping

@spmedia
Copy link
Author

spmedia commented Sep 12, 2017

Hey @sindresorhus, I'm still making progress on this slowly. Will aim to try and finish this week with:

  • Removing low-quality sites
  • Adding descriptions to each section & listings to add context

@pokeball99
Copy link
Contributor

@spmedia @sindresorhus is this PR ready to be merged yet?

@spmedia
Copy link
Author

spmedia commented Jan 25, 2018

I still need to clean it up a bit more :)

Feel free to help me add descriptions.

@sindresorhus
Copy link
Owner

Hey, sorry for the lack of response, please see #1363.

@sindresorhus
Copy link
Owner

Closing as the list still needs descriptions for most items and it doesn't seem like that will happen anytime soon. Feel free to resubmit when this is done and all the above requirements are fulfilled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants