PAGES
← all tools
◆ Reconnaissance & OSINT

metagoofil

v1.3.0 open-source

Metagoofil searches Google for specific file types publicly hosted on a domain and optionally downloads them locally.

source ↗ rss ↗ What is a cyber toolchain?

Summary

metagoofil is an open-source command-line tool that searches Google for specific file types hosted on a target domain and can download the results locally, useful for OSINTOSINTOpen-source intelligence, collecting and analyzing information from publicly available sources. Investigators use it to learn about people, infrastructure or threats. gathering, penetration testing, or checking what documents an organization is inadvertently exposing to search indexers. It runs from a cloned git repository or a Docker container, and it can be routed through proxychains when Google starts blocking repeated queries. Unlike the original project it forks from, it deliberately skips metadata analysis, deferring that step to tools like exiftool. It's aimed at penetration testers and OSINT researchers rather than defenders, and it ships pre-installed on Kali Linux. First committed in 2015 and still updated, with seven contributors and a release within the past year.

Metagoofil searches Google for specific file types publicly hosted on a domain and optionally downloads them locally.

How metagoofil helps

Which file types is a target organization unintentionally exposing to search engines?

runs a targeted Google query combining the domain and a chosen file extension, listing every publicly indexed document of that type it can find

Where can I get a local copy of everything a domain has leaked to Google for further review?

downloads the matching results to a local directory so they can be inspected or handed to another tool

What does the author, software, or template metadata in these leaked documents reveal?

it does not extract this itself, but names exiftool as the follow-on step to run against the downloaded files

Are my repeated lookups about to get blocked by Google?

repeated queries risk HTTP 429 responses, and routing lookups through proxychains and a bank of proxies avoids a single IP getting flagged

Would a defender scanning my traffic notice a bot pattern in these searches?

randomizes the User-Agent on both search queries and downloads instead of sending a static Googlebot string

all 4 features, with the evidence for each →

Languages

Not documented

Features

4 capabilities

Built from metagoofil'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 metagoofil offers you

  • Command-line interface
All capabilities 4 capabilities
User-Agent Randomization shipped Randomizes the User-Agent header for requests to mimic different clients, such as Googlebot. 1 release · first seen Feb 2025

release

  • Randomizes User-Agent header for both Google search queries and file downloads, replacing the static Googlebot string. v1.3.0 · Feb 2025 · source · release history
Google Search and Download documented suggested Searches Google for publicly hosted files on a target domain and optionally downloads them. 1 other source

Suggested capability: Attack surface inventory. This is our guess, not confirmed.

docs

  • Searches Google for publicly hosted files on a target domain and optionally downloads them for OSINT or penetration testing.
Metadata Extraction shipped Extracts metadata from downloaded documents for further analysis. 1 other source

example

  • Extract metadata from downloaded documents exiftool -r *.doc | egrep -i "Author|Creator|Email|Producer|Template" | sort -u
Proxy-based Search shipped Performs file type searches via proxychains to evade detection or access restrictions. 1 other source

example

  • Search via proxychains for multiple file types proxychains4 python metagoofil.py -d https://github.com -f -t pdf,doc,xls

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 metagoofil, 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 metagoofil 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

1 entry

  1. February 20251

    1 entry

    1. v1.3.0 Feb 8, 2025 · release notes

      metagoofil v1.3.0 randomizes User-Agent strings for Google searches and file downloads to reduce fingerprinting.

      └──▷ GET THIS VERSION 
      $ git clone --branch v1.3.0 https://github.com/opsdisk/metagoofil.git
# already have the repo? check out this version:
$ git checkout v1.3.0
      • Randomizes User-Agent header for both Google search queries and file downloads, replacing the static Googlebot string.

      1 detail in Everything

    Project health

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

    1. Contributors 0 −1 vs prior 12 months
    2. Maintainers 0 +0 joined · −1 left, last 12 months
    3. Bus factor 0 committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close not measured first maintainer reply 0.7 hours
    6. Open backlog 5 of 17 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 5
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 590
    Issue themes, last 12 months
    • other 100%

    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 →
    compare.md

      Free the public facts, no sign-in Any paid plan all other sections Researcher & Business pricing history and category rank

      my-toolchain — 0 tools

        Betas, release candidates and previews. Turn it off to see final releases only. It also applies to changes you ask for over MCP when you're signed in.
        browse all tools → score card for your toolchain →
        cyber-toolchain / feedback

        Send us feedback