Gathering detailed insights and metrics for @vscode/codicons
Gathering detailed insights and metrics for @vscode/codicons
Gathering detailed insights and metrics for @vscode/codicons
Gathering detailed insights and metrics for @vscode/codicons
vscode-codicons
This tool takes the Visual Studio Code icons and converts them into an font using the [icon-font-generator](https://github.com/Workshape/icon-font-generator). All icons are stored under `src > icons`. The mappings of the class names and unicode characters
vscode-ext-codicons
VS Code Codicons helper functions
@deephaven/icons
Icons used in Deephaven client apps. Extends vscode-codicons to be font-awesome svg-core compatible and adds additional icons in a similar style.
npm install @vscode/codicons
Typescript
Module System
Node Version
NPM Version
Handlebars (70.5%)
JavaScript (25.31%)
Dockerfile (4.2%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
CC-BY-4.0 License
978 Stars
534 Commits
197 Forks
21 Watchers
21 Branches
73 Contributors
Updated on Jul 09, 2025
Latest Version
0.0.36
Package Id
@vscode/codicons@0.0.36
Unpacked Size
1.16 MB
Size
448.13 kB
File Count
500
NPM Version
10.2.4
Node Version
18.19.1
Published on
May 09, 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
6
This tool takes the Visual Studio Code icons and converts them into an icon font using fantasticon.
You can use the npm package and install into your project via:
npm i @vscode/codicons
Note: We've deprecated vscode-codicons
in favor of @vscode/codicons
If you're building a VS Code extension, see this webview extension sample on how to integrate.
All icons are stored under src > icons
. The mappings of the class names and unicode characters are stored in src/template/mapping.json
as well as the default styles under src/template/styles.hbs
.
After cloning this repo, install dependencies by running:
npm install
npm run build
Output will be exported to a dist
folder.
You can run npm outdated
to see if there are any package updates. To update packages, run:
npm update
Export your icons (svg) to the src/icons
folder and add an entry into src/template/mapping.json
with a new codepoint key (this gets converted into a unicode key) and run the the build command. The build command will also remove any subfolders in the icons
folder to keep the folder structure consistent.
Next, update the codicons file on the vscode repository, ensuring that the unicode characters are the same (you can reference the css file).
If you're building a VS Code extension, see this webview extension sample on how to integrate.
When needing to reference an icon in the Visual Studio Code source code via CSS classes, simply create a dom element/container that contains codicon
and the icon name like:
1<div class='codicon codicon-add'></div>
It's recommended to use a single dom element for each icon and not to add children elements to it.
When needing to use the codicon.svg
sprite file, you can reference icons using the following method:
1<svg> 2 <use xlink:href="codicon.svg#add" /> 3</svg>
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Microsoft and any contributors grant you a license to the Microsoft documentation and other content in this repository under the Creative Commons Attribution 4.0 International Public License, see the LICENSE file, and grant you a license to any code in the repository under the MIT License, see the LICENSE-CODE file.
Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries. The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks. Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653.
Privacy information can be found at https://privacy.microsoft.com/en-us/
Microsoft and any contributors reserve all other rights, whether under their respective copyrights, patents, or trademarks, whether by implication, estoppel or otherwise.
No vulnerabilities found.
Reason
30 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Reason
all changesets reviewed
Reason
security policy file detected
Details
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
no binaries found in the repo
Reason
SAST tool is run on all commits
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
Project has not signed or included provenance with any releases.
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
23 existing vulnerabilities detected
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