Research Source Review compares your approved source passages

Name: Research Source Review
Author: theluckystrike

Compare approved paragraph text with the current source.

MIT · no telemetry · core features free

Approved text says 30 days while the current source paragraph says 14 days. — Open larger

version: 1.1.0
released: 2026-10-21
downloads: 21
review: Passed
health: Excellent
license: MIT
listed for: Desktop, Mobile
obsidian: 1.13.4 or later

The README reports desktop persistence checks through app restarts and plugin reloads. Phones, tablets, Linux, large vaults and concurrent sync writes were not tested.

Directory facts fetched 2026-10-23 07:28 UTC from community.obsidian.md/users/theluckystrike.

About Research Source Review

You base conclusions on passages in other Markdown notes and need to review those claims when source text changes.

A source paragraph can change after you use it to support a conclusion. Research Source Review saves the text you approved and compares it with a fresh read. You decide whether the conclusion needs work.

Pin a linked paragraph, run a manual scan, then inspect Approved text beside Current text. Scanning leaves the baseline intact until you select Mark checked.

Free features

Choose a linked paragraph

Run Pin a source paragraph from the active note to choose a link or embed with an explicit paragraph block ID. Read the passage, then select Save pin. Pins stay in local plugin data without edits to your source or dependent note.

The pin window shows a linked source paragraph ready for approval. — Open larger

Scan saved pins

Run Scan saved pins to compare current paragraphs with their saved text. An unrelated paragraph edit or moving the same paragraph within its source leaves its result unchanged.

An unchanged source passage matches the saved approved text. — Open larger

Compare before approval

The comparison uses literal Markdown, including internal spaces and line breaks, but excludes the block ID marker. Approval reads the source again. If the passage or saved baseline changed, you must review the refreshed comparison.

Keep the baseline when a block disappears

Missing sources, missing blocks and unsupported passages keep your approved text. Active rename events update saved paths; a rename while the plugin is off can leave a missing path.

A missing block result retains the previously approved source passage. — Open larger

Pro features

Pro costs $5 a month or $15 one time through GitHub Sponsors. One sponsorship turns on Pro in every plugin that has it.

Named review groups Pro

Create named project groups, assign pins and filter a scan by group. Group creation, assignment and filtering require Pro. Free scans still include pins from saved groups if Pro ends.

Saved pins belong to a named research review group. — Open larger

Dated local review reports Pro

Save dated report creates a Markdown note in your vault root after a fresh scan. It includes paths, check dates, statuses and approved and current text. Saving a report does not approve its passages.

A local Markdown report records the approved and current source text. — Open larger

See how Pro works

Set up Research Source Review

needs

Obsidian 1.13.4 or later

steps

Add 30 days ^limit as a separate paragraph in Source.md.
Link to it with [[Source#^limit]] in Conclusion.md, then open that note.
Run Pin a source paragraph from the active note, read the passage, then select Save pin.
After a source edit, run Scan saved pins and compare the approved and current text.
Review your conclusion, then select Mark checked to approve the displayed passage.

If the app can't find a new plugin yet, try again later. Obsidian says a plugin that passes the review shows in the app within 24 hours.

How to review changed source paragraphs in Obsidian

Known limits of Research Source Review

Only Markdown paragraphs with explicit block IDs are supported; headings, lists, quotes, tables, PDFs and images are excluded.
Scans are manual and detect literal local text changes, not claim accuracy, source reliability or remote article updates.
A source rename while the plugin is off can leave a missing path; repair the link and save a new pin.
Saved pins contain source text in local plugin data, and Pro reports contain source text and note paths in the vault.
Group creation, assignment and filtering require Pro; free scans still include pins from saved groups when Pro ends.
Phones, tablets, Linux, large vaults and concurrent writes from a sync service were not tested.

Questions about Research Source Review

Does this verify whether my conclusion is true?

The plugin detects literal changes in local source paragraphs. It doesn't assess a claim, source reliability or changes to a remote article.

Which source blocks can I pin?

Use Markdown paragraphs with explicit IDs at their ends. Headings, lists, quotes, tables and code blocks are excluded, as are PDF and image text.

What happens if I rename a source while the plugin is off?

Its saved path can become missing. Repair the link and save a new pin; the scan does not search for a replacement.

Where does the approved text stay?

Pins keep approved passages in local plugin data between plugin loads. Pro reports create notes containing source text and paths in the vault root.

Network use

Before you sign in, the plugin makes no network requests. Sign in sends a public client ID and read:user scope to github.com, then polls that host for an access token. Afterward, it sends the token and sponsorship queries to api.github.com; those requests include no note text, file names or vault data.

Read the full network disclosure