Gathering detailed insights and metrics for remark-lint-heading-style
Gathering detailed insights and metrics for remark-lint-heading-style
Gathering detailed insights and metrics for remark-lint-heading-style
Gathering detailed insights and metrics for remark-lint-heading-style
plugins to check (lint) markdown code style
npm install remark-lint-heading-style
Typescript
Module System
Node Version
NPM Version
remark-lint-no-unused-definitions@4.0.2
Updated on Apr 10, 2025
remark-lint-fenced-code-flag@4.2.0
Updated on Apr 09, 2025
remark-lint-no-undefined-references@5.0.2
Updated on Apr 09, 2025
10.0.1
Updated on Jan 27, 2025
remark-lint-table-cell-padding@5.1.0
Updated on Jan 27, 2025
remark-lint-table-pipe-alignment@4.1.0
Updated on Jan 27, 2025
JavaScript (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
987 Stars
629 Commits
135 Forks
19 Watchers
1 Branches
55 Contributors
Updated on Jul 13, 2025
Latest Version
4.0.1
Package Id
remark-lint-heading-style@4.0.1
Unpacked Size
15.74 kB
Size
4.66 kB
File Count
5
NPM Version
11.0.0
Node Version
23.1.0
Published on
Jan 27, 2025
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
remark-lint
rule to warn when headings violate a given style.
This package checks the style of headings.
You can use this package to check that the style of headings is consistent.
This plugin is included in the following presets:
Preset | Options |
---|---|
remark-preset-lint-consistent | 'consistent' |
remark-preset-lint-markdown-style-guide | 'atx' |
This package is ESM only. In Node.js (version 16+), install with npm:
1npm install remark-lint-heading-style
In Deno with esm.sh
:
1import remarkLintHeadingStyle from 'https://esm.sh/remark-lint-heading-style@4'
In browsers with esm.sh
:
1<script type="module"> 2 import remarkLintHeadingStyle from 'https://esm.sh/remark-lint-heading-style@4?bundle' 3</script>
On the API:
1import remarkLint from 'remark-lint' 2import remarkLintHeadingStyle from 'remark-lint-heading-style' 3import remarkParse from 'remark-parse' 4import remarkStringify from 'remark-stringify' 5import {read} from 'to-vfile' 6import {unified} from 'unified' 7import {reporter} from 'vfile-reporter' 8 9const file = await read('example.md') 10 11await unified() 12 .use(remarkParse) 13 .use(remarkLint) 14 .use(remarkLintHeadingStyle) 15 .use(remarkStringify) 16 .process(file) 17 18console.error(reporter(file))
On the CLI:
1remark --frail --use remark-lint --use remark-lint-heading-style .
On the CLI in a config file (here a package.json
):
1 … 2 "remarkConfig": { 3 "plugins": [ 4 … 5 "remark-lint", 6+ "remark-lint-heading-style", 7 … 8 ] 9 } 10 …
This package exports no identifiers.
It exports the TypeScript types
Options
and
Style
.
The default export is
remarkLintHeadingStyle
.
unified().use(remarkLintHeadingStyle[, options])
Warn when headings violate a given style.
options
(Options
, default: 'consistent'
)
— preferred style or whether to detect the first style and warn for
further differencesTransform (Transformer
from unified
).
Options
Configuration (TypeScript type).
1type Options = Style | 'consistent'
Style
Style (TypeScript type).
1type Style = 'atx' | 'atx-closed' | 'setext'
Setext headings are limited in that they can only construct headings with a rank of one and two. They do allow multiple lines of content where ATX only allows one line. The number of used markers in their underline does not matter, leading to either:
Hello\n-
),
which is the bare minimum,
and for rank 2 headings looks suspiciously like an empty list itemHello\n-----
),
which is hard to maintain and diffHello\n---
), which for rank 2 headings looks
suspiciously like a thematic breakSetext headings are also uncommon. Using a sequence of hashes at the end of ATX headings is even more uncommon. Due to this, it’s recommended to use ATX headings, without closing hashes.
remark-stringify
formats headings as ATX by default.
The other styles can be configured with setext: true
or closeAtx: true
.
ok.md
When configured with 'atx'
.
1# Mercury 2 3## Venus 4 5### Earth
No messages.
ok.md
When configured with 'atx-closed'
.
1# Mercury ## 2 3## Venus ## 4 5### Earth ###
No messages.
ok.md
When configured with 'setext'
.
1Mercury 2======= 3 4Venus 5----- 6 7### Earth
No messages.
not-ok.md
1Mercury 2======= 3 4## Venus 5 6### Earth ###
14:1-4:9: Unexpected ATX heading, expected setext 26:1-6:14: Unexpected ATX (closed) heading, expected setext
not-ok.md
When configured with '🌍'
.
11:1: Unexpected value `🌍` for `options`, expected `'atx'`, `'atx-closed'`, `'setext'`, or `'consistent'`
Projects maintained by the unified collective are compatible with maintained versions of Node.js.
When we cut a new major release, we drop support for unmaintained versions of
Node.
This means we try to keep the current release line,
remark-lint-heading-style@4
,
compatible with Node.js 16.
See contributing.md
in remarkjs/.github
for ways
to get started.
See support.md
for ways to get help.
This project has a code of conduct. By interacting with this repository, organization, or community you agree to abide by its terms.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
0 existing vulnerabilities detected
Reason
security policy file detected
Details
Reason
0 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 2/30 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More