Skip to content

Add OpenOSINT - AI-powered OSINT agent (username, email, IP, breach)#699

Open
SonoTommy wants to merge 1 commit into
lockfale:masterfrom
SonoTommy:master
Open

Add OpenOSINT - AI-powered OSINT agent (username, email, IP, breach)#699
SonoTommy wants to merge 1 commit into
lockfale:masterfrom
SonoTommy:master

Conversation

@SonoTommy

Copy link
Copy Markdown

OpenOSINT is an AI-powered OSINT agent that chains 14 intelligence
tools into a single automated workflow via an interactive REPL, CLI,
and MCP server.

Added to:

  • Username > Username Search Engines
  • Email Address > Email Search

Covers: username search across 300+ platforms (sherlock), email
enumeration (holehe), breach detection (HaveIBeenPwned), WHOIS,
subdomain discovery, IP geolocation, AbuseIPDB, Censys, Pastebin,
phone intel, and Google dork generation.

Runs locally — no API key required (Ollama supported).
MIT license. Python 3.10+.

https://github.com/OpenOSINT/OpenOSINT

Copilot AI review requested due to automatic review settings May 26, 2026 08:37

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds a new “OpenOSINT (T)” resource entry to public/arf.json.

Changes:

  • Added “OpenOSINT (T)” as a URL resource entry in two separate locations in the JSON file
  • Included a long-form description and marked the entry as local: true
Comments suppressed due to low confidence (2)

public/arf.json:1

  • The surrounding entries include fields like api, invitationOnly, and deprecated, but the new OpenOSINT (T) entry omits them. If consumers/schema assume these keys exist, this can break parsing or defaulting logic. Consider adding the same boolean fields to this object (with appropriate values) to keep the JSON schema consistent.
    public/arf.json:1
  • The same name/url entry is added twice in the file, but with different descriptions. This can cause duplicate results in UIs/search and makes future updates error-prone (two places to keep in sync). If this is meant to be one resource, deduplicate it; if it must appear in two sections, consider ensuring the descriptions are identical (or add a disambiguating field/name to clearly explain why there are two entries).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

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.

2 participants