Installations
npm install @figma/widget-typings
Releases
Unable to fetch releases
Developer
figma
Developer Guide
Module System
Unable to determine the module system for this package.
Min. Node Version
Typescript Support
Yes
Node Version
20.14.0
NPM Version
10.7.0
Statistics
11 Stars
104 Commits
6 Forks
59 Watching
25 Branches
18 Contributors
Updated on 22 Nov 2024
Languages
Shell (100%)
Total Downloads
Cumulative downloads
Total Downloads
638,067
Last day
-31.9%
924
Compared to previous day
Last week
-11.3%
5,348
Compared to previous week
Last month
0.2%
28,921
Compared to previous month
Last year
88.3%
375,252
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Peer Dependencies
1
Dev Dependencies
1
Figma Widget API typings
This repository contains the typings for the Figma Widget API.
Usage
-
Installation
Note that the widget api is an extention of the plugin api so you should install both
@figma/plugin-typings
and@figma/widget-typings
1npm i --save-dev @figma/plugin-typings @figma/widget-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 & widget 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 widget API is part of the host environment, as opposed to being a package that a plugin includes.
About
Widget 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.
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
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
0 existing vulnerabilities detected
Reason
Found 7/12 approved changesets -- score normalized to 5
Reason
4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
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
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/widget-typings/test.yml/main?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/widget-typings/test.yml/main?enable=pin
- Warn: npmCommand not pinned by hash: test-usage.sh:181
- Warn: npmCommand not pinned by hash: test-usage.sh:182
- Warn: npmCommand not pinned by hash: test-usage.sh:183
- Warn: npmCommand not pinned by hash: test-usage.sh:234
- Warn: npmCommand not pinned by hash: test-usage.sh:235
- Warn: npmCommand not pinned by hash: test-usage.sh:236
- 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 7 npmCommand dependencies pinned
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 'main'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 26 are checked with a SAST tool
Score
4.2
/10
Last Scanned on 2024-11-25
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