Installations
npm install @figma/plugin-typings
Developer Guide
Typescript
Yes
Module System
N/A
Node Version
22.10.0
NPM Version
10.9.0
Score
99.9
Supply Chain
81.4
Quality
98.3
Maintenance
100
Vulnerability
100
License
Releases
Unable to fetch releases
Contributors
Languages
Shell (100%)
Love this project? Help keep it running — sponsor us today! 🚀
Developer
figma
Download Statistics
Total Downloads
4,174,037
Last Day
1,447
Last Week
57,115
Last Month
232,142
Last Year
2,162,883
GitHub Statistics
MIT License
206 Stars
501 Commits
46 Forks
76 Watchers
30 Branches
69 Contributors
Updated on Feb 16, 2025
Package Meta Information
Latest Version
1.107.0
Package Id
@figma/plugin-typings@1.107.0
Unpacked Size
159.09 kB
Size
35.37 kB
File Count
10
NPM Version
10.9.0
Node Version
22.10.0
Published on
Feb 13, 2025
Total Downloads
Cumulative downloads
Total Downloads
4,174,037
Last Day
15.8%
1,447
Compared to previous day
Last Week
-10.7%
57,115
Compared to previous week
Last Month
48.1%
232,142
Compared to previous month
Last Year
68.9%
2,162,883
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dev Dependencies
1
Figma Plugin API typings
This repository contains the typings for the Figma Plugin API.
Usage
-
Installation
1npm i --save-dev @figma/plugin-typings 2# or 3yarn add -D @figma/plugin-typings
-
Configure tsconfig.json
1{ 2 "compilerOptions": { 3 "typeRoots": [ 4 "./node_modules/@types", 5 "./node_modules/@figma" 6 ] 7 } 8}
The configuration above is needed for the TypeScript compiler to use type definitions found in both
./node_modules/@types
and./node_modules/@figma
. Normally, most external type definitions are from DefinitelyTyped and are installed in/@types
, which included by TypeScript by default. Since we host the plugin typings separately, they are installed outside in/@figma
instead.Types should become globally available without needing to use import statements. We do it this way because the plugin API is part of the host environment, as opposed to being a package that a plugin includes.
About
Plugin API releases have the format "Version X, Update Y". Equivalent tags are created in this repository as v<x>.<y>
. Note that not all API releases include API changes, some are just bug fixes. Therefore, some typings versions are skipped.
![Empty State](/_next/static/media/empty.e5fae2e5.png)
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
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
Reason
Found 8/24 approved changesets -- score normalized to 3
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:8: update your workflow using https://app.stepsecurity.io/secureworkflow/figma/plugin-typings/test.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/figma/plugin-typings/test.yml/master?enable=pin
- Warn: npmCommand not pinned by hash: test-usage.sh:150
- Warn: npmCommand not pinned by hash: test-usage.sh:151
- Warn: npmCommand not pinned by hash: test-usage.sh:201
- Warn: npmCommand not pinned by hash: test-usage.sh:202
- Warn: npmCommand not pinned by hash: .github/workflows/test.yml:10
- Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 5 npmCommand dependencies pinned
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/test.yml:1
- Info: no jobLevel write permissions found
Reason
no effort to earn an OpenSSF best practices badge detected
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
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 'master'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 18 are checked with a SAST tool
Score
4.5
/10
Last Scanned on 2025-02-10
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