
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
Self-healing markdown. Intelligently parses and styles incomplete Markdown blocks.
Self-healing markdown. Intelligently parses and styles incomplete Markdown blocks.
Remend is a lightweight utility that handles incomplete Markdown syntax during streaming. When AI models stream Markdown token-by-token, you often get partial formatting markers like unclosed **bold** or incomplete [links](. Remend automatically completes these unterminated blocks so they render correctly in real-time.
Remend powers the markdown termination logic in Streamdown and can be used standalone in any streaming Markdown application.
Remend intelligently completes the following incomplete Markdown patterns:
**text → **text***text or _text → *text* or _text_***text → ***text***`code → `code`~~text → ~~text~~[text](url → [text](streamdown:incomplete-link)$$formula → $$formula$$$formula → $formula$ (opt-in, see inlineKatex)20~25 → 20\~25 (prevents false strikethrough)npm i remend
import remend from "remend";
// During streaming
const partialMarkdown = "This is **bold text";
const completed = remend(partialMarkdown);
// Result: "This is **bold text**"
// With incomplete link
const partialLink = "Check out [this link](https://exampl";
const completed = remend(partialLink);
// Result: "Check out [this link](streamdown:incomplete-link)"
You can selectively disable specific completions by passing an options object. Options default to true unless noted otherwise:
import remend from "remend";
// Disable link and KaTeX completion
const completed = remend(partialMarkdown, {
links: false,
katex: false,
});
Available options:
| Option | Description |
|---|---|
links | Complete incomplete links |
images | Complete incomplete images |
bold | Complete bold formatting (**) |
italic | Complete italic formatting (* and _) |
boldItalic | Complete bold-italic formatting (***) |
inlineCode | Complete inline code formatting (`) |
singleTilde | Escape single ~ between word characters to prevent false strikethrough (e.g. 20~25) |
strikethrough | Complete strikethrough formatting (~~) |
katex | Complete block KaTeX math ($$) |
inlineKatex | Complete inline KaTeX math ($) — defaults to false to avoid ambiguity with currency symbols |
setextHeadings | Handle incomplete setext headings |
handlers | Custom handlers to extend remend |
You can extend remend with custom handlers to complete your own markers during streaming. This is useful for custom syntax like <<<JOKE>>> blocks or other domain-specific patterns.
import remend, { type RemendHandler } from "remend";
const jokeHandler: RemendHandler = {
name: "joke",
handle: (text) => {
// Complete <<<JOKE>>> marks that aren't closed
const match = text.match(/<<<JOKE>>>([^<]*)$/);
if (match && !text.endsWith("<<</JOKE>>>")) {
return `${text}<<</JOKE>>>`;
}
return text;
},
priority: 80, // Runs after most built-ins (0-70)
};
const result = remend(content, { handlers: [jokeHandler] });
interface RemendHandler {
name: string; // Unique identifier
handle: (text: string) => string; // Transform function
priority?: number; // Lower runs first (default: 100)
}
Built-in handlers use priorities 0-75. Custom handlers default to 100 (run after built-ins):
| Handler | Priority |
|---|---|
singleTilde | 0 |
comparisonOperators | 5 |
htmlTags | 10 |
setextHeadings | 15 |
links | 20 |
boldItalic | 30 |
bold | 35 |
italic | 40-42 |
inlineCode | 50 |
strikethrough | 60 |
katex | 70 |
inlineKatex | 75 |
| Custom (default) | 100 |
Remend exports utility functions for context detection in custom handlers:
import {
isWithinCodeBlock,
isWithinMathBlock,
isWithinLinkOrImageUrl,
isWordChar,
} from "remend";
const handler: RemendHandler = {
name: "custom",
handle: (text) => {
// Skip if we're inside a code block
if (isWithinCodeBlock(text, text.length - 1)) {
return text;
}
// Your logic here
return text;
},
};
Remend is a preprocessor that must be run on the raw Markdown string before passing it into the unified/remark processing pipeline:
import remend from "remend";
import { unified } from "unified";
import remarkParse from "remark-parse";
import remarkRehype from "remark-rehype";
import rehypeStringify from "rehype-stringify";
const streamedMarkdown = "This is **incomplete bold";
// Run Remend first to complete incomplete syntax
const completedMarkdown = remend(streamedMarkdown);
// Then process with unified
const file = await unified()
.use(remarkParse)
.use(remarkRehype)
.use(rehypeStringify)
.process(completedMarkdown);
console.log(String(file));
This is important because Remend operates on the raw string level, while remark/unified work with abstract syntax trees (ASTs). Running Remend after parsing would be ineffective.
Remend analyzes the input text and:
The parser is designed to be defensive and only completes formatting when it's unambiguous that the block is incomplete.
Remend is built for high-performance streaming scenarios:
For more info, see the documentation.
FAQs
Self-healing markdown. Intelligently parses and styles incomplete Markdown blocks.
The npm package remend receives a total of 1,201,974 weekly downloads. As such, remend popularity was classified as popular.
We found that remend demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.