Free tool · works now

Markdown Link Inventory

Catalog all wikilinks, relative paths, web URLs, and image embeds in your notes without network calls.

Runs 100% in your browser. Extract, classify, and audit all web links, wikilinks, relative paths, and media embeds across your Markdown notes with strict code fence immunity and zero network calls.

Link Inventory & Audit Workbench

🔒 100% Browser-Local🛡️ Zero Outbound Pings💻 Code Block Immunity📊 9 Link Paradigms
Cataloged Links Inventory9 links found
LineTypeAnchor / TextDestinationDomain
22reference-definitionsec-rfchttps://datatracker.ietf.org/doc/html/rfc8259datatracker.ietf.org
4wikilinkSystem ArchitectureSystem Architecture⚠️internal-vault
4wikilinkProduction RunbookDeployment Runbook⚠️internal-vault
7inline-webCommonMark Specificationhttps://spec.commonmark.org/0.31.2/spec.commonmark.org
8autolinkhttps://www.getoyma.com/docshttps://www.getoyma.com/docswww.getoyma.com
9reference-linkAir-Gapped Note Securityhttps://datatracker.ietf.org/doc/html/rfc8259datatracker.ietf.org
10autolinkmailto:security@getoyma.commailto:security@getoyma.comgetoyma.com
19image-embedArchitecture Diagram./assets/diagram.pnglocal-relative
20image-embedworkflow-preview.pngworkflow-preview.pnginternal-vault
9Total Links
8Unique Targets
5External URLs
4Internal & Relative
2Syntax Warnings

The Architecture of Markdown Link Management: Cataloging, Classification, and Audit

1. The Evolution of Hyperlinks in Plain-Text Knowledge Bases

Hyperlinks are the primary connective tissue of modern digital knowledge bases. In the original 2004 Markdown specification created by John Gruber and Aaron Swartz, link syntax was designed to be easily readable in raw ASCII form while compiling cleanly into HTML anchor elements. Over the subsequent two decades, however, personal knowledge management (PKM) ecosystems, developer documentation engines, and static site generators introduced radically diverse linking paradigms.

Today, a single Markdown note repository frequently contains an intermingled mixture of standard inline links, CommonMark autolinks, reference-style link definitions, Obsidian-compatible bidirectional wikilinks, relative filesystem paths, and embedded images. Without dedicated inventory tools, vault authors cannot readily answer basic operational questions: How many external websites does this document depend upon? Which links are pointing to unencrypted HTTP endpoints? Are there orphaned reference link definitions whose anchors were deleted during editing?

2. Code Fence Immunity and Syntax Isolation Mechanics

The most critical vulnerability of naive link extraction tools is the failure to isolate code blocks. Software documentation, developer tutorials, and engineering runbooks frequently include code fences containing example link syntax. If an extractor uses crude regular expressions without token masking, it inadvertently catalogs example code links as live document references.

Our Markdown Link Inventory engine implements strict, deterministic code fence immunity. The parser operates in a two-stage pipeline:

  • Stage 1 (Code Token Masking): The engine scans for opening and closing code fence boundaries (three or more consecutive backticks ``` or tildes ~~~). Every character within a code fence is transformed into neutral space characters. In addition, inline backtick spans (`...`) are identified and masked out, ensuring inline code literals are completely neutralized.
  • Stage 2 (Grammar Classification): The masked buffer is evaluated against strict grammar extractors for autolinks, reference definitions, wikilinks, inline links, and image embeds. Line numbers and character offsets are preserved bit-for-bit from the original text, providing exact provenance for every cataloged link.

3. Nine Link Paradigms Compared

To maintain clarity across complex technical documentation, our inventory system classifies links into nine mutually exclusive structural categories:

Link ParadigmSyntax ExampleScope & BehaviorPrimary Use Case
Inline Web Link[Oyma](https://www.getoyma.com)External web navigationStandard documentation & article citations
Obsidian Wikilink[[Note Title|Alias]]Internal bidirectional vault graphPersonal knowledge management & Zettelkasten
CommonMark Autolink<https://example.com>Raw URL rendered as clickable anchorUnadorned web references and source links
Reference Link[Term][ref-id]Separates anchor text from URL targetAcademic citations & repeated URLs
Reference Definition[ref-id]: https://... "Title"Target URL lookup table at note bottomClean bottom footnotes and link dictionaries
Relative Local Path[Guide](./docs/setup.md)Local filesystem relative resolutionGit repository documentation & multi-file vaults
Image Embed![Alt](./assets/img.png)Media asset rendering in-placeVisual diagrams, screenshots, and figures
Mailto Scheme<mailto:team@domain.com>Launches local email clientContact sections and security vulnerability disclosures
Anchor Only[Jump to Top](#overview)Same-page DOM heading fragmentTable of contents navigation and longform guides

4. Security and Protocol Auditing Without External Pings

Corporate security policies, legal privilege requirements, and air-gapped data retention rules prohibit leaking note contents to third-party link-checking services. Many cloud-based link checkers perform automatic network GET or HEAD requests to external servers whenever a user pastes an article. This leaks proprietary hostnames, internal network IP addresses, and draft research topics across external server access logs.

Our utility executes 100% locally within your browser client. It performs zero outbound network requests. Instead, it audits links structurally by analyzing protocols and URL syntaxes:

  • Unencrypted HTTP Detection: Flags http:// endpoints that transmit data in plaintext without TLS encryption.
  • Dangerous Script Schemes: Catches malicious or accidental javascript: execution schemes that present Cross-Site Scripting (XSS) risks when converted to HTML.
  • Data URI Auditing: Identifies embedded data: payloads that inflate note sizes or conceal untracked payloads.
  • Unescaped Spaces: Identifies raw spaces within URL strings that break strict CommonMark parser adherence.
  • Unresolved Reference Keys: Flags shortcut links whose corresponding bottom definitions are missing.

5. Formula-Guarded CSV Export for Vault Audits

Large engineering organizations frequently export link catalogs into spreadsheet applications (such as Microsoft Excel, Apple Numbers, or Google Sheets) to conduct team-wide documentation audits. However, if a link target or anchor text starts with formula operator characters (such as =, +, -, or @), standard CSV imports can trigger dangerous Dynamic Data Exchange (DDE) or formula execution vulnerabilities.

The Markdown Link Inventory enforces strict formula defense. Every text field, target URL, and domain string starting with a formula trigger character is automatically escaped with a prepended single apostrophe (') and quoted securely. This ensures you can export thousands of links to CSV and analyze them in spreadsheet tools without security compromises.

Frequently Asked Questions

Questions

How does the inventory extractor distinguish links in prose from code snippets?

The engine parses Markdown in multiple isolated passes. Prior to any link regex matching, all fenced code blocks (delimited by triple backticks or tildes) and inline code backtick spans (`...`) are masked into neutral whitespace. This guarantees that code examples, tutorials, and configuration snippets containing Markdown link syntax never trigger false-positive catalog entries.

Does this tool send HTTP requests or ping the destinations to verify live status?

No. The Markdown Link Inventory executes 100% locally in your browser memory and never initiates outbound network calls. It performs structural syntax classification, protocol auditing (such as checking for unencrypted http:// or dangerous javascript: schemes), and domain aggregation completely offline without leaking your note content.

How does the parser handle Obsidian-style bidirectional wikilinks?

The extractor detects standard Obsidian wikilinks ([[Note Name]]) as well as piped aliases ([[Note Name|Display Label]]) and heading anchors ([[Note Name#Section]]). Wikilinks are categorized under the internal vault scope, allowing you to easily audit external internet dependencies separately from local personal knowledge graphs.

What is the difference between an autolink and an inline Markdown link?

CommonMark autolinks use angle bracket delimiters (<https://example.com> or <mailto:user@domain.com>) where the destination URL itself functions as the visible text. Inline links use square bracket anchor text followed by parenthesized URLs ([Anchor](https://example.com)). The inventory categorizes them into distinct types so you can maintain strict formatting consistency across your vault.

How does reference link shortcut resolution work?

Markdown supports reference-style links where an inline marker ([RFC 8259][rfc-json] or shortcut [rfc-json]) points to a definition placed elsewhere ([rfc-json]: https://...). The inventory engine indexes all reference definitions across the document and resolves shortcuts to their targets. Any reference link whose definition is missing is explicitly flagged with an unresolved-reference warning.

Maintain Clean, Durable Links Across Your Notes

Explore our browser-local tools for broken wikilink detection, relative path calculation, and URL sanitization.

tools markdown link inventory downloadDownload for Mac

No account needed. Intel Mac build