Gathering detailed insights and metrics for remark-github
Gathering detailed insights and metrics for remark-github
Gathering detailed insights and metrics for remark-github
Gathering detailed insights and metrics for remark-github
remark plugin to link references to commits, issues, pull-requests, and users, like on GitHub
npm install remark-github
97.2
Supply Chain
99.5
Quality
79.8
Maintenance
100
Vulnerability
100
License
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
180 Stars
220 Commits
22 Forks
9 Watching
1 Branches
20 Contributors
Updated on 28 Nov 2024
Minified
Minified + Gzipped
JavaScript (100%)
Cumulative downloads
Total Downloads
Last day
-0.9%
25,221
Compared to previous day
Last week
4.4%
153,653
Compared to previous week
Last month
8.6%
640,370
Compared to previous month
Last year
58%
7,289,098
Compared to previous year
remark plugin to link references to commits, issues, and users, in the same way that GitHub does in comments, issues, PRs, and releases (see Writing on GitHub).
This package is a unified (remark) plugin to link references to commits,
issues, and users: @wooorm
-> [**@wooorm**](https://github.com/wooorm)
.
This project is useful if you want to emulate how markdown would work in GitHub comments, issues, PRs, or releases, but it’s actually displayed somewhere else (on a website, or in other places on GitHub which don’t link references, such as markdown in a repo or Gist). This plugin does not support other platforms such as GitLab or Bitbucket and their custom features.
A different plugin, remark-gfm
, adds support for GFM (GitHub
Flavored Markdown).
GFM is a set of extensions (autolink literals, footnotes, strikethrough, tables,
and tasklists) to markdown that are supported everywhere on GitHub.
Another plugin, remark-breaks
, turns soft line endings
(enters) into hard breaks (<br>
s).
GitHub does this in a few places (comments, issues, PRs, and releases), but it’s
not semantic according to HTML and not compliant to markdown.
Yet another plugin, remark-frontmatter
, adds support
for YAML frontmatter.
GitHub supports frontmatter for files in Gists and repos.
This package is ESM only. In Node.js (version 16+), install with npm:
1npm install remark-github
In Deno with esm.sh
:
1import remarkGithub, {defaultBuildUrl} from 'https://esm.sh/remark-github@12'
In browsers with esm.sh
:
1<script type="module"> 2 import remarkGithub, {defaultBuildUrl} from 'https://esm.sh/remark-github@12?bundle' 3</script>
Say we have the following file example.md
:
1Some references:
2
3* Commit: f8083175fe890cbf14f41d0a06e7aa35d4989587
4* Commit (fork): foo@f8083175fe890cbf14f41d0a06e7aa35d4989587
5* Commit (repo): remarkjs/remark@e1aa9f6c02de18b9459b7d269712bcb50183ce89
6* Issue or PR (`#`): #1
7* Issue or PR (`GH-`): GH-1
8* Issue or PR (fork): foo#1
9* Issue or PR (project): remarkjs/remark#1
10* Mention: @wooorm
11
12Some links:
13
14* Commit: <https://github.com/remarkjs/remark/commit/e1aa9f6c02de18b9459b7d269712bcb50183ce89>
15* Commit comment: <https://github.com/remarkjs/remark/commit/ac63bc3abacf14cf08ca5e2d8f1f8e88a7b9015c#commitcomment-16372693>
16* Issue or PR: <https://github.com/remarkjs/remark/issues/182>
17* Issue or PR comment: <https://github.com/remarkjs/remark-github/issues/3#issue-151160339>
18* Mention: <https://github.com/ben-eb>
…and a module example.js
:
1import {remark} from 'remark' 2import remarkGfm from 'remark-gfm' 3import remarkGithub from 'remark-github' 4import {read} from 'to-vfile' 5 6const file = await remark() 7 .use(remarkGfm) 8 .use(remarkGithub) 9 .process(await read('example.md')) 10 11console.log(String(file))
…then running node example.js
yields:
1Some references:
2
3* Commit: [`f808317`](https://github.com/remarkjs/remark-github/commit/f8083175fe890cbf14f41d0a06e7aa35d4989587)
4* Commit (fork): [foo@`f808317`](https://github.com/foo/remark-github/commit/f8083175fe890cbf14f41d0a06e7aa35d4989587)
5* Commit (repo): [remarkjs/remark@`e1aa9f6`](https://github.com/remarkjs/remark/commit/e1aa9f6c02de18b9459b7d269712bcb50183ce89)
6* Issue or PR (`#`): [#1](https://github.com/remarkjs/remark-github/issues/1)
7* Issue or PR (`GH-`): [GH-1](https://github.com/remarkjs/remark-github/issues/1)
8* Issue or PR (fork): [foo#1](https://github.com/foo/remark-github/issues/1)
9* Issue or PR (project): [remarkjs/remark#1](https://github.com/remarkjs/remark/issues/1)
10* Mention: [**@wooorm**](https://github.com/wooorm)
11
12Some links:
13
14* Commit: [remarkjs/remark@`e1aa9f6`](https://github.com/remarkjs/remark/commit/e1aa9f6c02de18b9459b7d269712bcb50183ce89)
15* Commit comment: [remarkjs/remark@`ac63bc3` (comment)](https://github.com/remarkjs/remark/commit/ac63bc3abacf14cf08ca5e2d8f1f8e88a7b9015c#commitcomment-16372693)
16* Issue or PR: [remarkjs/remark#182](https://github.com/remarkjs/remark/issues/182)
17* Issue or PR comment: [#3 (comment)](https://github.com/remarkjs/remark-github/issues/3#issue-151160339)
18* Mention: <https://github.com/ben-eb>
This package exports the identifier defaultBuildUrl
.
The default export is remarkGithub
.
defaultBuildUrl(values)
Create a URL to GH.
values
(BuildUrlValues
)
— info on the link to buildURL to use (string
).
unified().use(remarkGithub[, options])
Link references to users, commits, and issues, in the same way that GitHub does in comments, issues, PRs, and releases.
options
(Options
, optional)
— configurationTransform (Transformer
).
BuildUrl
Create a URL (TypeScript type).
values
(BuildUrlValues
)
— info on the link to buildURL to use or false
to not link (string | false
).
BuildUrlCommitValues
Info for commit hash (TypeScript type).
hash
(string
)
— commit hash valueproject
(string
)
— project nametype
('commit'
)
— kinduser
(string
)
— owner of repoBuildUrlCompareValues
Info for commit hash ranges (TypeScript type).
base
(string
)
— SHA of the range startcompare
(string
)
— SHA of the range endproject
(string
)
— project nametype
('compare'
)
— kinduser
(string
)
— owner of repoBuildUrlIssueValues
Info for issues (TypeScript type).
no
(string
)
— issue numberproject
(string
)
— project nametype
('issue'
)
— kinduser
(string
)
— owner of repoBuildUrlMentionValues
Info for mentions (TypeScript type).
type
('mention'
)
— kinduser
(string
)
— user nameBuildUrlValues
Info (TypeScript type).
1type BuildUrlValues = 2 | BuildUrlCommitValues 3 | BuildUrlCompareValues 4 | BuildUrlIssueValues 5 | BuildUrlMentionValues
Options
Configuration (TypeScript type).
buildUrl
(BuildUrl
, default:
defaultBuildUrl
)
— change how things are linkedmentionStrong
(boolean
, default: true
)
— wrap mentions in strong
;
this makes them render more like how GitHub styles them, but GH itself
uses CSS instead of strong
repository
(string
, default: repository
from packag.json
in CWD in
Node, otherwise required)
— repository to link against;
should point to a GitHub repository (such as 'user/project'
)buildUrl
A buildUrl
can be passed to not link mentions.
For example, by changing example.js
from before like so:
1@@ -1,11 +1,15 @@ 2 import {remark} from 'remark' 3 import remarkGfm from 'remark-gfm' 4-import remarkGithub from 'remark-github' 5+import remarkGithub, {defaultBuildUrl} from 'remark-github' 6 import {read} from 'to-vfile' 7 8 const file = await remark() 9 .use(remarkGfm) 10- .use(remarkGithub) 11+ .use(remarkGithub, { 12+ buildUrl(values) { 13+ return values.type === 'mention' ? false : defaultBuildUrl(values) 14+ } 15+ }) 16 .process(await read('example.md')) 17 18 console.log(String(file))
To instead point mentions to a different place, change example.js
like so:
1@@ -1,11 +1,17 @@ 2 import {remark} from 'remark' 3 import remarkGfm from 'remark-gfm' 4-import remarkGithub from 'remark-github' 5+import remarkGithub, {defaultBuildUrl} from 'remark-github' 6 import {read} from 'to-vfile' 7 8 const file = await remark() 9 .use(remarkGfm) 10- .use(remarkGithub) 11+ .use(remarkGithub, { 12+ buildUrl(values) { 13+ return values.type === 'mention' 14+ ? `https://yourwebsite.com/${values.user}/` 15+ : defaultBuildUrl(values) 16+ } 17+ }) 18 .process(await read('example.md')) 19 20 console.log(String(file))
The following references are supported:
1f2a4fb
→
1f2a4fb
remarkjs@1f2a4fb
→
remarkjs@1f2a4fb
remarkjs/remark-github@1f2a4fb
→
remarkjs/remark-github@1f2a4fb
e2acebc...2aa9311
→
e2acebc...2aa9311
remarkjs@e2acebc...2aa9311
→
remarkjs/remark-github@e2acebc...2aa9311
remarkjs/remark-github@e2acebc...2aa9311
→
remarkjs/remark-github@e2acebc...2aa9311
GH-1
→
GH-1#1
→
#1remarkjs#1
→
remarkjs#1remarkjs/remark-github#1
→
remarkjs/remark-github#1@wooorm
→
@wooormAutolinks to these references are also transformed:
https://github.com/wooorm
-> [**@wooorm**](https://github.com/wooorm)
This package is fully typed with TypeScript.
It exports the additional types
BuildUrl
,
BuildUrlCommitValues
,
BuildUrlCompareValues
,
BuildUrlIssueValues
,
BuildUrlMentionValues
,
BuildUrlValues
,
DefaultBuildUrl
,
Options
.
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-github@^12
,
compatible with Node.js 16.
This plugin works with unified
version 6+ and remark
version 7+.
Use of remark-github
does not involve rehype (hast).
It does inject links based on user content, but those links only go to GitHub.
There are no openings for cross-site scripting (XSS) attacks.
remark-gfm
— support GFM (autolink literals, footnotes, strikethrough, tables,
tasklists)remark-breaks
— support breaks without needing spaces or escapes (enters to <br>
)remark-frontmatter
— support frontmatter (YAML, TOML, and more)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
0 existing vulnerabilities detected
Reason
license file detected
Details
Reason
security policy file detected
Details
Reason
Found 3/30 approved changesets -- score normalized to 1
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
no effort to earn an OpenSSF best practices badge detected
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 2024-11-18
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