PAGES
← all tools
◆ Reconnaissance & OSINT

linkedin2username

0.28 open-source

linkedin2username is an OSINTOSINTOpen-source intelligence, collecting and analyzing information from publicly available sources. Investigators use it to learn about people, infrastructure or threats. tool that scrapes LinkedIn company pages to generate lists of probable employee username formats without requiring an API key.

source ↗ rss ↗ What is a cyber toolchain?

Summary

linkedin2username is an open-source command-line tool that logs into LinkedIn with a valid user's credentials and scrapes a target company's employee list to generate probable username formats, and it costs nothing to use. It requires no API key, running instead as a local script against a real LinkedIn session via a browser Selenium can control, which makes it a fit for red teamers and social engineers building credential-stuffing or phishing target lists during recon. It sits in the OSINT reconnaissance space, alongside other username-enumeration and people-search tooling, producing plain text and CSV output ready to feed into other attack tooling. First committed in 2018 and still maintained by 14 contributors, it saw 5 commits in the past year and a release 93 days ago, so it remains active if not fast-moving.

linkedin2username is an OSINT tool that scrapes LinkedIn company pages to generate lists of probable employee username formats without requiring an API key.

How linkedin2username helps

What are the likely login usernames for employees at this target company?

logs into LinkedIn with real credentials and pulls every employee listed on the company's page, then generates first.last, f.last, flast, firstl, first, and lastf variants for each name into separate lists ready for spraying or stuffing

Who works at this company and what do they do?

writes a metadata file pairing each scraped employee's full name with their listed occupation, giving a role-sorted view of the target's staff

How do I turn a scraped name list into ready-to-use email addresses for a phishing run?

appends a supplied domain to every generated username variant so the output lines are already formatted as full email addresses

Am I at risk of LinkedIn flagging or rate-limiting the account I used for this recon?

the README notes rate limiting appears tied to hitting LinkedIn's commercial search limit and has so far only been temporary, measured on a monthly basis, rather than resulting in outright bans

all 3 features, with the evidence for each →

Languages

Not documented

Features

3 capabilities · 1 backed by code, an API document or a real run

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

  • Command-line interface1
All capabilities 3 capabilities
CLI interface verified Provides a command-line interface with options such as configurable output directory and built-in help. 2 releases · 2 other sources · first seen Nov 2022

Also counts toward: Command-line interface

release

  • Implements a new login workflow using Selenium to spawn an interactive browser session, resolving issues with challenges, abuse detection, and MFA requests. 0.28 · Sep 2023 · source · release history
  • Switches internal processing from regex-based extraction to proper JSON parsing 0.25 · Jan 2023 · source · release history

command line

Company employee enumeration shipped Scrapes company pages to identify probable username formats and lists employees with domain-appended usernames. 3 other sources

docs

  • OSINT tool that scrapes LinkedIn company pages to generate lists of probable employee username formats.

example

  • Pull all employees of a target company python linkedin2username.py -c targetco
  • Short list with domain appended to usernames python linkedin2username.py -c targetco -d 5 -n 'targetco.com'
Profile metadata extraction shipped Outputs a metadata file containing additional details, such as job titles, for discovered profiles. 1 release · first seen Jan 2023

release

  • Adds metadata.txt file output that includes the headline (typically a job title) for each discovered profile 0.25 · Jan 2023 · source · release history

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 linkedin2username, 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 linkedin2username 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. September 20231
  3. January 20231

    2 entries

    1. 0.28 Sep 3, 2023 · release notes

      linkedin2username 0.28 introduces Selenium-based interactive browser login to bypass MFAMFAMulti-factor authentication, requiring proof from different categories, such as a password and a hardware key, to sign in. It reduces reliance on a password alone. and abuse detection

      └──▷ GET THIS VERSION 
      $ git clone --branch 0.28 https://github.com/initstring/linkedin2username.git
# already have the repo? check out this version:
$ git checkout 0.28
      • Implements a new login workflow using Selenium to spawn an interactive browser session, resolving issues with challenges, abuse detection, and MFA requests.

      1 detail in Everything

    2. 0.25 Jan 24, 2023 · release notes

      linkedin2username 0.25 adds metadata.txt output with profile headlines and switches to JSON parsing.

      └──▷ GET THIS VERSION 
      $ git clone --branch 0.25 https://github.com/initstring/linkedin2username.git
# already have the repo? check out this version:
$ git checkout 0.25
      • Adds metadata.txt file output that includes the headline (typically a job title) for each discovered profile
      • Switches internal processing from regex-based extraction to proper JSON parsing

      2 details in Everything

    Project health

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

    1. Contributors 1 +1 vs prior 12 months
    2. Maintainers 1 +1 joined · −0 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close 57 days first maintainer reply 57 days
    6. Open backlog 0 of 40 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 0
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 1,856
    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