PAGES
← all tools
◆ Reconnaissance & OSINT

maryam

V.1.5 open-source

OWASPOWASPA nonprofit foundation that publishes open standards, guides, and ranked vulnerability lists—most famously the OWASP Top 10—giving cyber tools a vendor-neutral benchmark to test or report against. Maryam is a modular open-source framework based on OSINTOSINTOpen-source intelligence, collecting and analyzing information from publicly available sources. Investigators use it to learn about people, infrastructure or threats. and data gathering to harvest data from open sources and search engines.

Summary

maryam is an open-source OSINT framework, licensed under GPLv3, that harvests data from open sources and search engines for reconnaissance work. It runs as a command-line tool written in Python, installable via pip, with modules invoked through an -e flag for tasks like DNS search and brute-forcing, Google and YouTube queries, or exposing the same functions through a small web API. It's aimed at people doing footprinting and information-gathering ahead of an assessment, such as OSINT practitioners or red teamers building a target profile, rather than at teams monitoring their own external attack surfaceattack surfaceThe exposed systems, interfaces and access points an attacker could try to use. It includes internet-facing services as well as identities, software and other reachable resources.. Development is not active: first committed in 2019 with 30 contributors, but no commits in the past year and its last release over 700 days ago.

OWASP Maryam is a modular open-source framework based on OSINT and data gathering to harvest data from open sources and search engines.

How maryam helps

What DNS records and subdomains actually exist for this domain?

brute-forces and queries DNS against the target domain across multiple threads and returns the resolved records, with the option to dump the full result set as JSON

What has this organization exposed across search engines that I should fold into a target profile?

runs the same query against engines like Google and YouTube through their public search interfaces and returns the matched pages or videos for the practitioner to review

Which reconnaissance techniques do I have available for a given target type?

lists the framework's modules so a practitioner can see the harvesting and brute-forcing tasks already built rather than writing a new scraper

How do I fold this data-gathering into a script or another tool I'm running?

exposes the same modules over a small local web API, so a query can be issued over HTTP and the results consumed as JSON instead of read off a terminal

How do I get exhaustive results instead of a quick sample when profiling a domain?

takes an all-resources option that tells a module to exhaust its available sources rather than stopping at the first page of results

all 7 features, with the evidence for each →

Languages

Not documented

Features

7 capabilities

Built from maryam's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What maryam offers you

  • Command-line interface1
  • JSON data export1
All capabilities 7 capabilities
Framework module listing shipped Provides a command to list all available modules within the framework. 3 releases · 2 other sources · first seen Jan 2021

Also counts toward: Command-line interface

release

  • Enables running modules with options directly without entering the interactive framework V.1.4.9 · Jan 2021 · source · release history
  • Removes the limit from global options, allowing unlimited configuration values V.1.4.9 · Jan 2021 · source · release history
  • Adds update_check to global options to control whether the tool checks for updates on startup V.1.4.9 · Jan 2021 · source · release history

example

  • Disable automatic update checks on startup by setting the new global option. maryam --update-check false V.1.4.9 · Jan 2021 · source
  • List all available framework modules maryam -e show modules
Instagram OSINT search shipped Allows querying Instagram for metadata or user information to harvest data. 1 release · 1 other source · first seen Mar 2021

release

example

  • Query Instagram metadata or user info via the CLI. maryam -m instagram <target_user_or_query> V.1.5 · Mar 2021 · source
Stack Overflow OSINT search shipped Allows searching Stack Overflow for technical questions and answers to harvest data. 1 release · 1 other source · first seen Mar 2021

release

  • stack overflow module added for Stack Overflow data access V.1.5 · Mar 2021 · source · release history

example

  • Search Stack Overflow for technical questions and answers. maryam -m stackoverflow <search_keyword> V.1.5 · Mar 2021 · source
DNS brute-forcing shipped suggested Performs brute-force attacks against DNS records for a given domain. 1 other source

Suggested capability: DNS record enumeration. This is our guess, not confirmed.

example

  • Brute-force DNS records for a domain maryam -e dnsbrute -d domain.tld
Google OSINT search shipped Allows searching Google for specific queries to harvest data. 1 other source

example

  • Search Google for a query maryam -e google -q "<QUERY>"
Multi-threaded DNS search shipped suggested Executes DNS searches with multi-threading and outputs results in JSON format. 1 other source

Suggested capability: DNS record enumeration. This is our guess, not confirmed.

Also counts toward: JSON data export

example

  • DNS search with multi-threading and JSON output maryam -e dns_search -d ibm.com -t 5 --max --api --form
YouTube OSINT search shipped Allows searching YouTube for specific queries to harvest data. 1 other source

example

  • Search YouTube for a query maryam -e youtube -q "<QUERY>"

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for maryam, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail maryam puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

2 entries

  1. March 20211
  2. January 20211

    2 entries

    Project health

    Issue, contributor and maintainer activity in saeeddhqan/Maryam, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 0 ±0 vs prior 12 months
    2. Maintainers 0 +0 joined · −0 left, last 12 months
    3. Bus factor 0 committers behind half the commits
    4. Community-filed not measured of issues opened, last 12 months
    5. Median time to close not measured issues closed, last 12 months
    6. Open backlog 1 of 130 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 1
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 1,233
    Issue themes, last 12 months not measured

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →