Gathering detailed insights and metrics for remark-numbered-footnotes
Gathering detailed insights and metrics for remark-numbered-footnotes
Gathering detailed insights and metrics for remark-numbered-footnotes
Gathering detailed insights and metrics for remark-numbered-footnotes
Live demo: https://zestedesavoir.github.io/zmarkdown/
npm install remark-numbered-footnotes
Typescript
Module System
Node Version
NPM Version
zmarkdown@12.1.0
Updated on Jun 14, 2025
zmarkdown@12.0.0
Updated on Apr 27, 2024
rebber-plugins@4.4.0
Updated on Apr 27, 2024
rebber@5.5.0
Updated on Apr 27, 2024
zmarkdown@11.4.3
Updated on Apr 20, 2024
rebber-plugins@4.3.9
Updated on Apr 20, 2024
JavaScript (98.39%)
HTML (1.06%)
CSS (0.42%)
Shell (0.14%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
230 Stars
1,223 Commits
53 Forks
11 Watchers
3 Branches
31 Contributors
Updated on Jul 03, 2025
Latest Version
3.1.1
Package Id
remark-numbered-footnotes@3.1.1
Unpacked Size
7.56 kB
Size
2.86 kB
File Count
5
NPM Version
lerna/8.1.2/node@v20.12.0+x64 (linux)
Node Version
20.12.0
Published on
Apr 27, 2024
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
1
This plugin replaces the footnote references with a number sequence (starting from 1) in the same order as the footnote definitions (not the footnote references).
Reordering the definitions (usually put at the end of the document in the Markdown source) will therefore let you reorder the sequence.
This is useful if you want your footnotes to be superscript numbers without having to manually enter them while keeping the benefit of using strings that make sense to you in your Markdown source.
If you are using this plugin, your project is most certainly relying on mdast-util-to-hast. Run npm ls mdast-util-to-hast
if you're unsure.
Starting from mdast-util-to-hast@6.0.0
, the footnote order changed. Before 6.0.0
, footnotes were following the order in which they were defined, starting from 6.0.0
they follow the order of the references.
1a[^first_footnote_reference] 2 3b[^`b` second footnote reference but first footnote definition] 4 5c[^last_footnote_reference] 6 7[^last_footnote_reference]: `c` last footnote reference but second footnote definition 8[^first_footnote_reference]: `a` first footnote reference but last footnote definition
Before 6.0.0
:
After 6.0.0
:
In the HTML ordered list, the list items 1/2/3 don't match the footnote references numbers anymore.
To avoid this issue you can either use older versions of your dependencies (not recommended) or visit the HAST tree after mdast-util-to-hast
to fix the footnote orders (recommended).
Here is an example.
This way the above markdown will always generate HTML with matching footnote list items and footnote numbered references as can be seen below:
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
dependency not pinned by hash detected -- score normalized to 4
Details
Reason
2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Reason
Found 3/22 approved changesets -- score normalized to 1
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
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
Reason
42 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-06-30
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