Gathering detailed insights and metrics for @spectrum-web-components/number-field
Gathering detailed insights and metrics for @spectrum-web-components/number-field
Spectrum Web Components
Installations
npm install @spectrum-web-components/number-fieldDeveloper Guide
BETA
Typescript
Yes
Module System
ESM
Node Version
20.16.0
NPM Version
10.8.1
Releases
Unable to fetch releases
Languages
6
TypeScript
CSS
JavaScript
HTML
Handlebars
MDX
TypeScript (66.41%)
CSS (31.37%)
JavaScript (2.07%)
HTML (0.08%)
Handlebars (0.06%)
Developer
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
Apache-2.0 License
1,405 Stars
4,923 Commits
229 Forks
46 Watchers
250 Branches
342 Contributors
Updated on Jul 17, 2025
Maintainers
7
Package Meta Information
Latest Version
1.7.0
Package Id
@spectrum-web-components/number-field@1.7.0
Unpacked Size
327.19 kB
Size
47.91 kB
File Count
33
NPM Version
10.8.1
Node Version
20.16.0
Published on
Jun 11, 2025
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
8
Dev Dependencies
1
Overview
<sp-number-field> elements are used for numeric inputs.
Usage
yarn add @spectrum-web-components/number-field
Import the side effectful registration of <sp-number-field> via:
import '@spectrum-web-components/number-field/sp-number-field.js';
When looking to leverage the NumberField base class as a type and/or for extension purposes, do so via:
import { NumberField } from '@spectrum-web-components/number-field';
Anatomy
A number field consists of an input field for numeric values and optional stepper buttons for incrementing and decrementing the value. The stepper UI can be hidden using the hide-stepper attribute.
1<sp-field-label> 2 What is the air-speed velocity of an unladen swallow? 3</sp-field-label> 4<sp-number-field 5 id="anatomy" 6 format-options='{ 7 "style": "unit", 8 "unit": "MPH", 9 "unitDisplay": "long" 10 }' 11></sp-number-field>
Options
Sizes
1<sp-number-field label="Size" value="1024" size="s"></sp-number-field>
1<sp-number-field label="Size" value="1024" size="m"></sp-number-field>
1<sp-number-field label="Size" value="1024" size="l"></sp-number-field>
1<sp-number-field label="Size" value="1024" size="xl"></sp-number-field>
Formatting
An <sp-number-field> element will process its numeric value with new Intl.NumberFormat(this.resolvedLanguage, this.formatOptions).format(this.value) in order to prepare it for visual delivery in the input. In order to customize this processing supply your own Intl.NumberFormatOptions via the formatOptions property, or format-options attribute as seen below.
this.resolvedLanguage represents the language in which the <sp-number-field> element is currently being delivered. By default, this value will represent the language established by the lang attribute on the root <html> element while falling back to navigator.language when that is not present. This value can be customized via a language context provided by a parent element that listens for the sp-language-context event and supplies update language settings to the callback function contained therein. Applications leveraging the <sp-theme> element to manage the visual delivery or text direction of their content will be also be provided a reactive context for supplying language information to its descendants.
The following example uses the signDisplay option to include the plus sign for positive numbers, for example to display an offset from some value. In addition, it always displays a minimum of 1 digit after the decimal point, and allows up to 2 fraction digits. If the user enters more than 2 fraction digits, the result will be rounded.
1<sp-field-label for="decimals">Adjust exposure</sp-field-label> 2<sp-number-field 3 id="decimals" 4 value="0" 5 format-options='{ 6 "signDisplay": "exceptZero", 7 "minimumFractionDigits": 1, 8 "maximumFractionDigits": 2 9 }' 10></sp-number-field>
The style: 'percent' option can be passed to the formatOptions property to treat the value as a percentage. In this mode, the value is multiplied by 100 before it is displayed, i.e. 0.45 is displayed as "45%". The reverse is also true: when the user enters a value, the change event will be triggered with the entered value divided by 100. When the percent option is enabled, the default step automatically changes to 0.01 such that incrementing and decrementing occurs by 1%. This can be overridden with the step property.
1<sp-field-label for="percents">Sales tax</sp-field-label> 2<sp-number-field 3 id="percents" 4 value="0.05" 5 format-options='{ 6 "style": "percent" 7 }' 8></sp-number-field>
The style: 'currency' option can be passed to the formatOptions property to treat the value as a currency value. The currency option must also be passed to set the currency code (e.g. USD) to use. In addition, the currencyDisplay option can be used to choose whether to display the currency symbol, currency code, or currency name. Finally, the currencySign option can be set to accounting to use accounting notation for negative numbers, which uses parentheses rather than a minus sign in some locales.
If you need to allow the user to change the currency, you should include a separate dropdown next to the sp-number-field. The sp-number-field itself will not determine the currency from the user input.
1<sp-field-label for="currency">Transaction amount</sp-field-label> 2<sp-number-field 3 id="currency" 4 value="45" 5 format-options='{ 6 "style": "currency", 7 "currency": "EUR", 8 "currencyDisplay": "code", 9 "currencySign": "accounting" 10 }' 11></sp-number-field>
The style: 'unit' option can be passed to the formatOptions property to format the value with a unit of measurement. The unit option must also be passed to set which unit to use (e.g. inch). In addition, the unitDisplay option can be used to choose whether to display the unit in long, short, or narrow format.
If you need to allow the user to change the unit, you should include a separate dropdown next to the number field. The number field itself will not determine the unit from the user input.
Note: The unit style is not currently supported in Safari. A polyfill may be necessary.
1<sp-field-label for="units">Package width</sp-field-label> 2<sp-number-field 3 id="units" 4 value="4" 5 format-options='{ 6 "style": "unit", 7 "unit": "inch", 8 "unitDisplay": "long" 9 }' 10></sp-number-field>
While Intl.NumberFormatOptions does support a wide range of units, it is possible to encounter units (e.g. the graphics units of pixel, pixels, points, etc.) that are not supported therein. When this occurs, an <sp-number-field> element will attempt to polyfill support for this unit. See the following example delivering { style: "unit", unit: "px" } below:
1<sp-field-label for="units">Document width in pixels</sp-field-label> 2<sp-number-field 3 id="units" 4 value="500" 5 format-options='{ 6 "style": "unit", 7 "unit": "px" 8 }' 9></sp-number-field>
Note: the polyfilling done here is very simplistic and is triggered by supplying options that would otherwise cause the Intl.NumberFormat() call to throw an error. Once the unsupporting unit of px causes the construction of the object to throw, a back up formatter/parser pair will be created without the supplied unit data. When the style is set to unit, the unit value of will be adopted as the static unit display. This means that neither pluralization or translation will be handled within the <sp-number-field> element itself. If pluralization or translation is important to the delivered interface, please be sure to handle passing those strings into to element via the formatOptions property reactively to the value of the element or locale of that page in question.
The min and max properties can be used to limit the entered value to a specific range. The value will be clamped when the user commits the value to the <sp-number-field> element. In addition, the increment and decrement buttons will be disabled when the value is within one step value from the bounds. Ranges can be open ended by only providing a value for either min or max rather than both.
If a valid range is known ahead of time, it is a good idea to provide it to <sp-number-field> so it can optimize the experience. For example, when the minimum value is greater than or equal to zero, it is possible to use a numeric keyboard on iOS rather than a full text keyboard (necessary to enter a minus sign).
1<sp-field-label for="red">Red value</sp-field-label> 2<sp-number-field id="red" value="4" min="0" max="255"></sp-number-field>
The step prop can be used to snap the value to certain increments. If there is a min defined, the steps are calculated starting from that minimum value. For example, if min === 2, and step === 3, the valid step values would be 2, 5, 8, 11, etc. If no min is defined, the steps are calculated starting from zero and extending in both directions. In other words, such that the values are evenly divisible by the step. A step can be any positive decimal. If no step is defined, any decimal value may be typed, but incrementing and decrementing snaps the value to an integer.
If the user types a value that is between two steps and blurs the input, the value will be snapped to the nearest step. When incrementing or decrementing, the value is snapped to the nearest step that is higher or lower, respectively. When incrementing or decrementing from an empty field, the value starts at the minValue or maxValue, respectively, if defined. Otherwise, the value starts from 0.
1<sp-field-label 2 for="step" 3>Step</sp-field-label> 4<sp-number-field 5 id="step" 6 step="10" 7></sp-number-field> 8 9<sp-field-label 10 for="step-min" 11>Step + min</sp-field-label> 12<sp-number-field 13 id="step-min" 14 min="2" 15 step="3" 16></sp-number-field> 17 18<sp-field-label 19 for="step-min-max" 20>Step + min + max</sp-field-label> 21<sp-number-field 22 id="step-min-max" 23 min="2" 24 max="21" 25 step="3" 26></sp-number-field>
States
Invalid
The invalid attribute indicates that the number field's value is invalid. When set, appropriate ARIA attributes will be automatically applied.
1<sp-field-label for="invalid"> 2 It's one banana, Michael, how much could it cost? 3</sp-field-label> 4<sp-number-field 5 id="invalid" 6 invalid 7 style="width: 130px" 8 value="10" 9 min="0" 10 max="0.3" 11 step="0.01" 12 format-options='{ 13 "style": "currency", 14 "currency": "USD", 15 "currencyDisplay": "code", 16 "currencySign": "accounting", 17 "minimumFractionDigits": 2, 18 "maximumFractionDigits": 2 19 }' 20></sp-number-field> 21<sp-help-text variant="negative"> 22 Value should be between $0 and $0.3. 23</sp-help-text>
Valid
The valid attribute indicates that the number field's value is valid.
1<sp-field-label for="valid"> 2 It's one banana, Michael, how much could it cost? 3</sp-field-label> 4<sp-number-field 5 id="valid" 6 valid 7 style="width: 130px" 8 value="0.23" 9 min="0" 10 max="0.3" 11 step="0.01" 12 format-options='{ 13 "style": "currency", 14 "currency": "USD", 15 "currencyDisplay": "code", 16 "currencySign": "accounting", 17 "minimumFractionDigits": 2, 18 "maximumFractionDigits": 2 19 }' 20></sp-number-field>
Required
Use the required attribute to indicate a number field value is required. Dictate the validity or invalidity state of the text entry with the valid or invalid attributes.
1<sp-field-label for="number-1" required>Count</sp-field-label> 2<sp-number-field id="number-1" valid value="123"></sp-number-field> 3<sp-field-label for="number-2" required>Size</sp-field-label> 4<sp-number-field id="number-2" invalid value="152"></sp-number-field>
Disabled
The disabled attribute prevents the number field from receiving focus or events. The number field will appear faded.
1<sp-field-label for="disabled" disabled>Number of tickets</sp-field-label> 2<sp-number-field id="disabled" disabled value="0"></sp-number-field>
Read-only
Number fields have a readonly attribute for when they’re in the disabled state but still need their labels to be shown. This allows for content to be copied, but not interacted with or changed.
1<sp-field-label for="readonly">Number of tickets</sp-field-label> 2<sp-number-field id="readonly" readonly value="0"></sp-number-field>
Behaviors
The number field works with the following interactions:
- the input field,
- ArrowUp or ArrowDown keys,
- the scroll wheel, or
- the stepper UI, when not hidden by the
hide-stepperattribute.
The input value incrementally increases or decreases by the value of the step attribute. The shift key can be used to apply steps at 10 times (or the value of the step-modifier attribute times) their normal rate.
Default value
The <sp-number-field> component doesn't manage a default value by itself. This means that consumers can set the value of the number-field as an empty string by clearing the input. If we want the number-field to reset to a default-value when the user clears the input, we can listen for the change event on the number-field component and set its value to the desired default-value if the input is empty.
1<sp-field-label for="default"> 2 Default value of this number field is 42 3</sp-field-label> 4<sp-number-field id="default" value="20"></sp-number-field> 5 6<script type="module"> 7 const numberField = document.querySelector('#default'); 8 9 numberField.addEventListener('change', (event) => { 10 alert('change'); 11 const target = event.target; 12 if (isNaN(target.value)) { 13 target.value = '42'; 14 } 15 }); 16</script>
Accessibility
Labels
Every number field must have a label that clearly describes its purpose. The label can be provided either via the label attribute or with an associated <sp-field-label> element.
Keyboard Navigation
Number fields support the following keyboard interactions:
- ArrowUp and ArrowDown keys increment and decrement the value
- Shift + ArrowUp or ArrowDown applies steps at 10 times (or the value of
step-modifier) the normal rate - The scroll wheel can be used to increment and decrement the value when focused
Help Text
Consider providing help text to explain:
- The expected format of the input
- Any minimum or maximum values
- The meaning of units or special formatting (e.g., currency, percentages)
- Step increments if they differ from the default
No vulnerabilities found.
Reason
30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: Apache License 2.0: LICENSE:0
Reason
no binaries found in the repo
Reason
security policy file detected
Details
- Info: security policy file detected: github.com/adobe/.github/.github/SECURITY.md:1
- Info: Found linked content: github.com/adobe/.github/.github/SECURITY.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: github.com/adobe/.github/.github/SECURITY.md:1
- Info: Found text in security policy: github.com/adobe/.github/.github/SECURITY.md:1
Reason
Found 24/28 approved changesets -- score normalized to 8
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Info: jobLevel 'pull-requests' permission set to 'read': .github/workflows/lint.yml:46
- Info: jobLevel 'contents' permission set to 'read': .github/workflows/pr-update.yml:12
- Info: topLevel 'contents' permission set to 'read': .github/workflows/browser-tests.yml:8
- Info: topLevel 'contents' permission set to 'read': .github/workflows/chromatic-vrt.yml:18
- Warn: no topLevel permission defined: .github/workflows/coveralls.yml:1
- Info: topLevel 'contents' permission set to 'read': .github/workflows/lint.yml:22
- Warn: no topLevel permission defined: .github/workflows/pr-update.yml:1
- Info: topLevel 'contents' permission set to 'read': .github/workflows/preview-docs.yml:10
- Warn: no topLevel permission defined: .github/workflows/preview-release.yml:1
- Warn: no topLevel permission defined: .github/workflows/publish-docs-site.yml:1
- Info: topLevel 'contents' permission set to 'read': .github/workflows/urls-smoke-test.yml:10
- Info: no jobLevel write permissions found
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/browser-tests.yml:75: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/browser-tests.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/browser-tests.yml:80: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/browser-tests.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/browser-tests.yml:87: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/browser-tests.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/browser-tests.yml:93: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/browser-tests.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/browser-tests.yml:24: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/browser-tests.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/browser-tests.yml:29: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/browser-tests.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/browser-tests.yml:58: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/browser-tests.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/chromatic-vrt.yml:31: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/chromatic-vrt.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/chromatic-vrt.yml:46: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/chromatic-vrt.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/coveralls.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/coveralls.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/coveralls.yml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/coveralls.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/lint.yml:50: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/lint.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/lint.yml:54: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/lint.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/lint.yml:75: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/lint.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/lint.yml:80: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/lint.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/lint.yml:92: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/lint.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/lint.yml:107: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/lint.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/lint.yml:118: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/lint.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/pr-update.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/pr-update.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/pr-update.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/pr-update.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/preview-docs.yml:29: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/preview-docs.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/preview-docs.yml:34: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/preview-docs.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/preview-docs.yml:54: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/preview-docs.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/preview-release.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/preview-release.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/publish-docs-site.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/publish-docs-site.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/urls-smoke-test.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/urls-smoke-test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/urls-smoke-test.yml:39: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/urls-smoke-test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/urls-smoke-test.yml:83: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/urls-smoke-test.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/urls-smoke-test.yml:99: update your workflow using https://app.stepsecurity.io/secureworkflow/adobe/spectrum-web-components/urls-smoke-test.yml/main?enable=pin
- Info: 0 out of 23 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 6 third-party GitHubAction dependencies pinned
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
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
Reason
36 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-28mc-g557-92m7
- Warn: Project is vulnerable to: GHSA-968p-4wvh-cqc8
- Warn: Project is vulnerable to: GHSA-jr5f-v2jv-69x6
- Warn: Project is vulnerable to: GHSA-qwcr-r2fm-qrc7
- Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw
- Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
- Warn: Project is vulnerable to: GHSA-pxg6-pf52-xh8x
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-67mh-4wv8-2f99
- Warn: Project is vulnerable to: GHSA-qw6h-vgh9-j6wx
- Warn: Project is vulnerable to: GHSA-pfq8-rq6v-vf5m
- Warn: Project is vulnerable to: GHSA-c7qv-q95q-8v27
- Warn: Project is vulnerable to: GHSA-4www-5p9h-95mh
- Warn: Project is vulnerable to: GHSA-9gqv-wp59-fq42
- Warn: Project is vulnerable to: GHSA-2p57-rm9w-gvfp
- Warn: Project is vulnerable to: GHSA-593f-38f6-jp5m
- Warn: Project is vulnerable to: GHSA-x2rg-q646-7m2v
- Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
- Warn: Project is vulnerable to: GHSA-mwcw-c2x4-8c55
- Warn: Project is vulnerable to: GHSA-3h52-269p-cp9r
- Warn: Project is vulnerable to: GHSA-9wv6-86v2-598j
- Warn: Project is vulnerable to: GHSA-rhx6-c78j-4q9w
- Warn: Project is vulnerable to: GHSA-x7hr-w5r2-h6wg
- Warn: Project is vulnerable to: GHSA-gcx4-mw62-g8wm
- Warn: Project is vulnerable to: GHSA-m6fv-jmcg-4jfg
- Warn: Project is vulnerable to: GHSA-76p7-773f-r4q5
- Warn: Project is vulnerable to: GHSA-cm22-4g7w-348p
- Warn: Project is vulnerable to: GHSA-w5hq-hm5m-4548
- Warn: Project is vulnerable to: GHSA-cvv5-9h9w-qp2m
- Warn: Project is vulnerable to: GHSA-pq67-2wwv-3xjx
- Warn: Project is vulnerable to: GHSA-8cj5-5rvv-wf4v
- Warn: Project is vulnerable to: GHSA-7p7h-4mm5-852v
- Warn: Project is vulnerable to: GHSA-4vvj-4cpr-p986
- Warn: Project is vulnerable to: GHSA-4v9v-hfq4-rm2v
- Warn: Project is vulnerable to: GHSA-9jgg-88mc-972h
- Warn: Project is vulnerable to: GHSA-3h5v-q93c-6h6q
Score
5.3
/10
Last Scanned on 2025-07-14
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