Gathering detailed insights and metrics for remark-slug-anchor
Gathering detailed insights and metrics for remark-slug-anchor
Package to work with remark-slug to generate clickable anchor icons
Installations
npm install remark-slug-anchorDeveloper Guide
BETA
Typescript
Yes
Module System
ESM
Node Version
12.22.6
NPM Version
6.14.15
Releases
3
Languages
2
TypeScript
SCSS
TypeScript (76.88%)
SCSS (23.12%)
Developer
ghostdevv
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
NOASSERTION License
30 Commits
1 Watchers
3 Branches
1 Contributors
Updated on Sep 30, 2022
Maintainers
1
Package Meta Information
Latest Version
1.0.0
Package Id
remark-slug-anchor@1.0.0
Unpacked Size
5.56 kB
Size
2.66 kB
File Count
6
NPM Version
6.14.15
Node Version
12.22.6
Total Downloads
Cumulative downloads
Total Downloads
NaN
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
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
3
Peer Dependencies
1
Dev Dependencies
5
Remark Slug Anchor
Automatically append anchor tags to your header elements.
Your code:
1# Hello World
Your page:
Install
This package is ESM only:
Node 12+ is needed to use it and it must be imported instead of required.
1npm install remark-slug-anchor remark-slug
You can now use this along with remark-slug (must use), you can find an example here of how to use remark-slug - include this package in the same way
You also need to import that css file, if you are using a preprocessor/bundler you can import from the package remark-slug-anchor/dist/anchor.css, if not use the cdn:
1<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/remark-slug-anchor@0/dist/anchor.css" />
Options / Styling
We had to switch from embedding a svg to inline and due to that limitation styling isn't really possible on the svg itself
To pass in options do this:
1import remarkSlugAnchor from 'remark-slug-anchor'; 2import remarkSlug from 'remark-slug'; 3 4const plugins = [ 5 remarkSlug, 6 [remarkSlugAnchor, { /* options */ }] 7]
Options:
-
color:
You can set the color of the anchor (if using built in anchor) with this optionNOTE: You must use an absolute colour, you are unable to use something like
var(--color), anything like rgb, rgba, hex, built ins, etc are supported -
icon:
You can pass in your own svg icon, with this optionMust be a string as it's encoded to be used as an anchor
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Warn: project license file does not contain an FSF or OSI license.
Reason
4 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw
- Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:11: update your workflow using https://app.stepsecurity.io/secureworkflow/ghostdevv/remark-slug-anchor/release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:12: update your workflow using https://app.stepsecurity.io/secureworkflow/ghostdevv/remark-slug-anchor/release.yml/main?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/release.yml:17
- Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 npmCommand dependencies pinned
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/26 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/release.yml:1
- Info: no jobLevel write permissions found
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'main'
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 4 are checked with a SAST tool
Score
3
/10
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