@gr4vy/secure-fields

中文文档
2.13.0发布于 2026/11/03MITTypeScriptESM + CJS近 30 天下载 5.2万

Gr4vy-hosted secure fields offering advanced theming, PCI compliance, event handling, and more.

原始使用文档
文档目录22 节
  1. Usage
  2. Get started
  3. Reset
  4. Validation
  5. Auto focus
  6. Input masking
  7. Auto advance
  8. Scheme icons
  9. Styles
  10. Events
  11. Global events
  12. Field events
  13. Click to Pay
  14. Prerequisites
  15. Adding Click to Pay
  16. Additional Global events
  17. Updating Checkout Options
  18. API reference
  19. Getters
  20. Methods
  21. Field methods
  22. Field options

Secure Fields

NPM Version GitHub license Changelog

Add Secure Fields to your Node app.

Use @gr4vy/secure-fields-react in a React application or @gr4vy/secure-fields-cdn in non-Node web application.

Usage

Via the command line, install this package as follows.

npm install @gr4vy/secure-fields --save-prod
# yarn add @gr4vy/secure-fields --save

Get started

To use Secure Fields, you need some placeholder elements to attach the secure fields on to. Each of these elements will be replaced by a secure field. These elements can be <input> but do not need to be.

<label for="cc-number">Card Number</label>
<input id="cc-number" />

<label for="cc-cvv">Security code</label>
<input id="cc-cvv" />

<label for="cc-expiry">Expiry date</label>
<input id="cc-expiry" />

<button id="cc-button">Submit</button>

To use Secure Fields, call the new SecureFields() method with a configuration object that includes the environment (sandbox or production), your gr4vyId and a sessionId obtained from calling the Checkout Sessions API. An optional paymentMethod object with id and scheme can also be passed to use Secure Fields with a stored payment method.

Then, add the fields and event listeners needed to handle the form submission.

const { SecureFields } = require('@gr4vy/secure-fields')

// Alternatively
// import { SecureFields } from '@gr4vy/secure-fields'

const secureFields = new SecureFields({
  gr4vyId: '[GR4VY_ID]',
  environment: 'sandbox',
  sessionId: '[SESSION_ID]',

  // For stored payment methods (optional):
  // paymentMethod: {
  //   id: '[PAYMENT_METHOD_ID]',
  //   scheme: 'visa' // Enables accurate CVV validation (3 digits for Visa/Mastercard, 4 for Amex)
  // },

  // Deprecated:
  // paymentMethodId: '[PAYMENT_METHOD_ID]', // uuid of a stored payment method
})

secureFields.addFont('Lato')

const styles = {
  color: 'black',
  fontSize: '18px',
  fontFamily: 'Lato',
  ':focus': {
    color: 'blue',
  },
}

const number = secureFields.addCardNumberField('#cc-number', { styles })
const expiry = secureFields.addExpiryDateField('#cc-expiry', { styles })
const cvv = secureFields.addSecurityCodeField('#cc-cvv', { styles })

secureFields.addEventListener(SecureFields.Events.CARD_VAULT_SUCCESS, () =>
  console.log('Card tokenized successfully')
)

secureFields.addEventListener(
  SecureFields.Events.CARD_VAULT_FAILURE,
  (data) => console.log('Card tokenization failed', data) // data.status, data.code, data.message
)

number.addEventListener('input', (data) => {
  console.warn('Input changed', data) // data.schema, data.codeLabel...
})

const button = document.querySelector('#cc-button')
button.addEventListener('click', () => {
  secureFields.submit()
})

Note: Replace [GR4VY_ID] with your Gr4vy ID and [SESSION_ID] with a valid checkout session id.

This will initialize Secure Fields and replace each of the inputs with a corresponding secure element. On submit, it will store the card data securely with Gr4vy, after which you can create a transaction or vault the card for later use.

You can also collect other kind of information along with the card data. We currently support an additional postal code field, which can be added to your form using the addField method, passing the specific type and the rest of the options.

<!-- placeholder HTML code -->
<label for="postal-code">Postal code</label>
<input id="postal-code" />
// js code
const postalCode = secureFields.addField('#postal-code', {
  type: 'postalCode',
  pattern: '[A-Z][0-9]\\s[0-9][A-Z]{2}', // optional, defaults to 5 characters minimum
  maxlength: 7 // optional, defaults to no maximum length
  styles,
  ...
})

postalCode.addEventListener('input', (data) => {
  console.warn('Input changed', data)
})

Reset

Each field instance exposes a clear() method to reset the value programmatically.

const number = secureFields.addCardNumberField('#cc-number', { styles })

const clearButton = document.querySelector('#clear-button')
clearButton.addEventListener('click', () => number.clear())

Validation

By default a field is flagged invalid once the user leaves it. Call validate() to flag every invalid field at once, including empty ones the user never touched, for example when the user clicks "Pay". Use the complete property of the FORM_CHANGE event to stop the submission if the form isn't ready.

let complete = false
secureFields.addEventListener(SecureFields.Events.FORM_CHANGE, (data) => {
  complete = data.complete
})

payButton.addEventListener('click', () => {
  secureFields.validate()
  if (secureFields.method === 'card' && !complete) return
  secureFields.submit()
})

To show no errors until validate() is called, set validateOn to 'submit' before adding fields. After that, errors update as the user types.

secureFields.setValidateOn('submit')

Each field in the FORM_CHANGE event also reports touched (blurred or validated at least once) and dirty (value changed at least once, by typing or by browser autofill).

Auto focus

Automatically focus a field once its iframe is loaded by passing autoFocus: true.

const number = secureFields.addCardNumberField('#cc-number', {
  autoFocus: true,
  styles,
})

Input masking

Mask the value of card number and security code fields to hide sensitive data.

const number = secureFields.addCardNumberField('#cc-number', {
  maskInput: {
    character: '•', // masking character (default: •)
    showLastFour: true, // keep last 4 digits visible when valid (card number only)
    maskOnInput: true, // mask in real-time as the user types (default: on blur only)
  },
  styles,
})

You can also mask and unmask a field programmatically:

number.redactValue() // mask the value
number.unredactValue() // unmask the value

Auto advance

Automatically move focus to the next field when the current field is complete and valid.

secureFields.setAutoAdvance({
  enabled: true,
  fieldOrder: ['number', 'expiryDate', 'securityCode'], // optional, defines the order of fields
})

Note: Auto advance can negatively affect the user experience. Test thoroughly before enabling in production.

Scheme icons

Display card scheme icons inside the card number field. Icons update in real-time as the user types and are refined when the API confirms the scheme.

Pass true to show the detected scheme icon along with any additional schemes (e.g. co-branded cards):

const number = secureFields.addCardNumberField('#cc-number', {
  showSchemeIcons: true,
  styles,
})

For granular control, pass an object to choose which icons to display:

const number = secureFields.addCardNumberField('#cc-number', {
  showSchemeIcons: {
    scheme: true, // show the detected card scheme icon (default: false)
    additionalSchemes: true, // show additional scheme icons, e.g. co-branded (default: false)
    placeholders: true, // show placeholder icons (Visa, Mastercard, Amex) before detection (default: false)
  },
  styles,
})

Note: A maximum of 3 icons are visible at any time. In co-branded scenarios, the primary scheme icon is displayed first, followed by additional schemes. Ensure the card number input is wide enough to accommodate up to 3 icons.

For more information please refer to the Secure Fields get started guide.

Styles

The outer styling of every Secure Field is completely in your control by applying your own CSS to the following class names.

/* Applied to each field */
.secure-fields__input {
}
/* Applied to the card number field */
.secure-fields__input--number {
}
/* Applied to the expiry date field */
.secure-fields__input--expiry-date {
}
/* Applied to the security code field */
.secure-fields__input--security-code {
}
/* Applied to the postal code field */
.secure-fields__input--postal-code {
}
/* Applied to a focused field */
.secure-fields__input[data-secure-fields-focused] {
}
/* Applied to an invalid field */
.secure-fields__input[data-secure-fields-invalid] {
}
/* Applied to an autofilled field */
.secure-fields__input[data-secure-fields-autofilled] {
}

To set the CSS of the content of a field an object of CSS rules can be passed to the addCardNumberField, addExpiryDateField, addSecurityCodeField and addField methods.

const styles = {
  // Default styles applied to field
  color: "#66666",
  fontSize: "1.3em",
  // ...etc

  // Applied when field has a value autofilled by browser/extension
  ':autofill': { ... },
  // Applied when field is hovered
  ':hover': { ... },
  // Applied when field is focused
  ':focus': { ... },
  // Applied when field is disabled
  ':disabled': { ... },
  // Applied when field is valid
  ':valid': { ... },
  // Applied when field is invalid
  ':invalid': { ... },
  // Applied to field placeholder
  '::placeholder': { ... },
}

Not all CSS properties can be set. The currently supported list is as follows.

backgroundColor
boxShadow
caretColor
color
colorScheme
cursor
font
fontFamily
fontFeatureSettings
fontKerning
fontSize
fontSizeAdjust
fontStretch
fontStyle
fontVariant
fontVariantAlternates
fontVariantCaps
fontVariantEastAsian
fontVariantLigatures
fontVariantNumeric
fontVariationSettings
fontWeight
letterSpacing
lineHeight
opacity
padding
textAlign
textShadow
textRendering
transition
MozOsxFontSmoothing
WebkitFontSmoothing

Events

Global events

The following events can be listened to by attaching an event handler to the SecureFields instance using the addEventListener method.

NameDescriptionExample
CARD_VAULT_SUCCESSTriggered when the card is successfully vaulted.secureFields.addEventListener(SecureFields.Events.CARD_VAULT_SUCCESS, () => { console.log('Card has been tokenized successfully!') })
CARD_VAULT_FAILURETriggered when the card vaulting fails.secureFields.addEventListener(SecureFields.Events.CARD_VAULT_FAILURE, ({ code, status, message }) => { console.log('Couldn\'t tokenize the card', { code, status, message }) })
FORM_CHANGETriggered when one of the form field is changed. The complete property shows if the form is ready to be submitted, i.e. card number and expiry date are filled and valid.secureFields.addEventListener(SecureFields.Events.FORM_CHANGE, ({ complete, fields }) => { console.log('Form state', { complete, fields }) })
READYTriggered when Secure Fields is loaded and ready to be used.secureFields.addEventListener(SecureFields.READY, () => { console.log('Secure fields loaded') })

Field events

The following events can be listened to by attaching an event handler to a field (returned by the addCardNumberField, addExpiryDateField, addSecurityCodeField and addField methods) using the addEventListener method.

Some of these provide additional useful data like the card BIN, validation status, and scheme. For example, the input event on a card number field might include { schema: 'visa', codeLabel: 'CVV', valid: true, ... }.

NameDescriptionExample
blurTriggered when the field loses focus.cardNumberField.addEventListener('blur', (data) => { console.log(data) /* { id: 'number' } */ })
focusTriggered when the field gains focus.cardNumberField.addEventListener('focus', (data) => { console.log(data) /* { id: 'number' } */ })
inputTriggered when the field value has been changed.cardNumberField.addEventListener('input', (data) => { console.log(data) /* { id: 'number', schema: 'visa', codeLabel: 'CVV', valid: true, empty: true, autofilled: false, bin: '411111' } */
redactedTriggered when the field value has been masked (either automatically via maskInput or programmatically via redactValue()).cardNumberField.addEventListener('redacted', () => { console.log('Field redacted') })
unredactedTriggered when the field value has been unmasked (either automatically or programmatically via unredactValue()).cardNumberField.addEventListener('unredacted', () => { console.log('Field unredacted') })
card-details-changedTriggered when the API confirms card details for the entered BIN. Includes the confirmed scheme, additionalSchemes (co-branded networks), and other card metadata. Only fires on the card number field.cardNumberField.addEventListener('card-details-changed', (data) => { console.log(data) /* { id: 'number', scheme: 'visa', additionalSchemes: ['mastercard'], ... } */ })

Click to Pay

Click to Pay is the better way to pay online – featuring advanced payment technology built on secure remote commerce industry standards.

Prerequisites

Follow the instructions for Click to Pay Merchant Setup.

Adding Click to Pay

Once Secure Fields is configured, you can start adding Click to Pay to your checkout.

Firstly, add a placeholder component to your form so Secure Fields knows where to render the Click to Pay component.

Then, add a simple sign-in form to let users access their Click to Pay stored cards.

Additionally, add a checkbox to allow a customer not already enrolled to determine if they want to share the card data with Click to Pay or not.

Finally, ensure card inputs are wrapped with a container element (e.g. <form />) with a specific id.

<div id="click-to-pay"></div>

<div id="click-to-pay-sign-in" style="display: none;">
  <label>Access your Click to Pay stored cards</label>
  <input type="text" id="phoneOrEmail" />
  <button id="signInButton">Continue</button>
</div>

<form id="card-form" style="display: none;">
  <label htmlFor="cc-number">Card number</label>
  <input type="text" id="cc-number" />

  <label htmlFor="cc-expiry-date">Expiry date</label>
  <input type="text" id="cc-expiry-date" />

  <label htmlFor="cc-security-code">Security code</label>
  <input type="text" id="cc-security-code" />
</form>

<input type="checkbox" id="click-to-pay-consent-checkbox" />
<label for="click-to-pay-consent-checkbox"
  >Store my card with Click to Pay</label
>

<script>
  var phoneOrEmail = document.querySelector('#phoneOrEmail')
  var signInButton = document.querySelector('#signInButton')
  signInButton.addEventListener('click', function () {
    clickToPay.signIn({ email: phoneOrEmail.value })
  })
</script>

Next, attach the secure field for Click to Pay to this element. This will require the email and/or phone number of the user you want to create a transaction for. It also requires an HTML query for the consent checkbox that controls if the card data for a new card is shared with Click to Pay or not.

const clickToPay = secureFields.addClickToPay('#click-to-pay', {
  dpaLocale: 'en_AU',
  cardBrands: ['mastercard', 'visa', 'american-express'],
  email: '[email protected]',
  mobileNumber: {
    countryCode: '61',
    phoneNumber: '491570159',
  },
  consentCheckbox: '#click-to-pay-consent-checkbox',
  signIn: '#click-to-pay-sign-in',
  cardForm: '#card-form',
})
// clickToPay = { element: <div id="click-to-pay" />, signIn: ..., options: { dpaName: ... } }

The available Click to Pay options are the following:

Option NameDescription
srcDpaIdDPA Identifier. This is a unique identifier for you Digital Payment Application (DPA), which was generated during onboarding.
dpaNameLegal name of registered DPA.
cardBrandsList of card schemes the merchant accepts. We currently support mastercard, maestro, visa, amex, discover
cardFormA reference to the card form wrapper.
signInA reference to the sign-in elements wrapper.
consentCheckboxA reference to the opt-in consent checkbox element.
learnMoreLinkA reference to the learn more link element.
emailThe user email used to access Click to Pay.
mobileNumberThe user phone number used to access Click to Pay. Required format is { countryCode: string, phoneNumber: string }
dynamicDataTypeThe type of cryptogram or token used for the card data. See the Mastercard docs for more information. Possible values are NONE and CARD_APPLICATION_CRYPTOGRAM_SHORT_FORM. Defaults to CARD_APPLICATION_CRYPTOGRAM_SHORT_FORM.

Additional Global events

The following Click to Pay events can be listened to by attaching an event handler to the SecureFields instance using the addEventListener method.

NameDescriptionExample
CLICK_TO_PAY_INITIALIZEDTriggered when Click to Pay has been initialized.secureFields.addEventListener(SecureFields.Events.CLICK_TO_PAY_INITIALIZED, (clickToPay) => { console.log('Click to Pay initialized', clickToPay) })
CLICK_TO_PAY_READYTriggered when Click to Pay is ready.secureFields.addEventListener(SecureFields.Events.CLICK_TO_PAY_READY, ({ buyerExists }) => { console.log('Click to Pay ready', { buyerExists }) })
CLICK_TO_PAY_SIGN_OUTTriggered when a user signs out of Click to Pay.secureFields.addEventListener(SecureFields.Events.CLICK_TO_PAY_SIGN_OUT, ({ buyerExists }) => { console.log('User signed out') })
CLICK_TO_PAY_ERRORTriggered when Click to Pay throws an error.secureFields.addEventListener(SecureFields.Events.CLICK_TO_PAY_ERROR, (error) => { console.log('Click to Pay error', error) }) // "RETRIES_EXCEEDED" | "CODE_INVALID" | "INVALID_CARD" | "SIGN_OUT_FAILED" | "ACCT_INACCESSIBLE" | "UNKNOWN" | "USER_NOT_RECOGNIZED" |
CLICK_TO_PAY_CANCELTriggered when a user closes / cancels Click to Pay.secureFields.addEventListener(SecureFields.Events.CLICK_TO_PAY_CANCEL, () => { console.log('User cancelled Click to Pay') })
CLICK_TO_PAY_CHECKOUT_WITH_NEW_CARDTriggered when a user performs the checkout with a new card (not yet enrolled in Click to Pay).secureFields.addEventListener(SecureFields.Events.CLICK_TO_PAY_CHECKOUT_WITH_NEW_CARD, () => { console.log('User is using a new card') })
CLICK_TO_PAY_UNABLE_TO_LOAD_DPATriggered when the provided Click to Pay DPA cannot be loaded.secureFields.addEventListener(SecureFields.Events.CLICK_TO_PAY_UNABLE_TO_LOAD_DPA, () => { console.log('Unable to load Click to Pay DPA') })
CLICK_TO_PAY_VISIBILITY_CHANGETriggered when the Click to Pay element is shown or hidden.secureFields.addEventListener(SecureFields.Events.CLICK_TO_PAY_VISIBILITY_CHANGE, (visible) => { console.log('Click to Pay element is ' + visible ? "visible" : "not visible") })
CLICK_TO_PAY_CARD_FORM_VISIBILITY_CHANGETriggered when the card form container is shown or hidden.secureFields.addEventListener(SecureFields.Events.CLICK_TO_PAY_CARD_FORM_VISIBILITY_CHANGE, (visible) => { console.log('Card form is ' + visible ? "visible" : "not visible") })
CLICK_TO_PAY_SIGN_IN_VISIBILITY_CHANGETriggered when the sign in container is shown or hidden.secureFields.addEventListener(SecureFields.Events.CLICK_TO_PAY_SIGN_IN_VISIBILITY_CHANGE, (visible) => { console.log('Sign in is ' + visible ? "visible" : "not visible") })
METHOD_CHANGETriggered when the user selects a different method (either card or click-to-pay)secureFields.addEventListener(SecureFields.Events.METHOD_CHANGE, (method) => { console.log('Selected method changed', method) })

Updating Checkout Options

Update the Click to Pay checkout options after initialization. This is useful when the transaction amount changes (e.g. cart updates) before the user submits.

secureFields.clickToPay.updateCheckoutOptions({
  transactionAmount: 9.99,
  transactionCurrencyCode: 'AUD',
})

Options are merged with previously set values, so you can update individual fields without losing the rest.

// Set initial options
secureFields.clickToPay.updateCheckoutOptions({
  transactionAmount: 9.99,
  transactionCurrencyCode: 'AUD',
})

// Later, update only the amount — currency is preserved
secureFields.clickToPay.updateCheckoutOptions({
  transactionAmount: 12.99,
})
OptionTypeDescription
transactionAmountnumberThe transaction amount.
transactionCurrencyCodestringThe transaction currency code.

API reference

Getters

NameDescription
EventsGives access to the supported events.

SecureFields.Events.READY
versionReturns the current version of the instance.

SecureFields.version

Methods

NameDescription
constructorInstantiates SecureFields with a configuration object include environment, gr4vyId and a session id. An optional paymentMethod object with id and scheme can also be passed to use Secure Fields with a stored payment method.

new SecureFields({...})
addCardNumberFieldInjects a secure field of type number.

secureFields.addCardNumberField('#cc-number', { placeholder: 'Enter card number', ... })
addSecurityCodeFieldInjects a secure field of type securityCode.

secureFields.addSecurityCodeField('#cc-security-code', { placeholder: 'Enter security code', ... })
addExpiryDateFieldInjects a secure field of type expiryDate.

secureFields.addExpiryDateField('#cc-expiry-date', { placeholder: 'Enter expiry date', ... })
addFieldAllows to inject secure fields based on type, for example a postal code field.

secureFields.addField('#postal-code', { type: 'postalCode', placeholder: 'Enter postal code', ... })
addClickToPayInjects a field that initializes Click to Pay.

secureFields.addClickToPay('#click-to-pay', { dpaLocale: 'en_AU', cardBrands: ['mastercard', 'visa'], ... })
addEventListenerAttaches an event handler to the SecureFields instance or to a secure field in order to listen to specific events. Requires one of the events supported and a callback.

secureFields.addEventListener(SecureFields.Events.READY, (data) => { ... })

cardNumberField.addEventListener('input', (data) => { ... })
removeEventListenerRemoves a previously attached event handler.
submitCalls the Vault API to tokenize and store the card data.

secureFields.submit()
setDebugEnable / disable debug mode. When the debug mode is enabled, SecureFields logs information to the console.

secureFields.setDebug(true)
addFontLoad a custom font from Google Fonts to be used inside inputs. You can define the font family as well as styles or weights as a string (e.g. "Lato:400,600"). To use the loaded font, add the correct fontFamily property to the styles object when creating fields.

secureFields.addFont('Lato')
validateFlags every invalid field, including empty ones the user never touched, and marks all fields as touched.

secureFields.validate()
setValidateOnSets when fields show validation errors: 'blur' (default), once the user leaves a field, or 'submit', once validate() is called.

secureFields.setValidateOn('submit')
setAutoAdvanceEnable auto-advance to automatically move focus to the next field when the current field's value is complete and valid. Accepts { enabled: boolean, fieldOrder?: Array<FieldType> }.

secureFields.setAutoAdvance({ enabled: true })

Field methods

NameDescription
clearResets the value of a field.

cardNumberField.clear()
redactValueMasks the field value programmatically. To apply masking behavior, configure maskInput for the field.

cardNumberField.redactValue()
unredactValueUnmasks the field value programmatically. To apply masking behavior, configure maskInput for the field.

cardNumberField.unredactValue()

Field options

The following options can be passed when adding a field (e.g. addCardNumberField('#el', options)).

NameTypeDescription
placeholderstringInput placeholder text.
stylesobjectCSS styles for the input inside the iframe.
labelstringAccessible label for the input.
autoFocusbooleanAutomatically focus the field when loaded.
maskInputboolean | objectEnable input masking. Use true for default masking, or pass an options object: character (masking character), showLastFour (card number only), maskOnInput (real-time mask).
showSchemeIconsboolean | objectDisplay card scheme icons inside the card number field. Icons update in real-time as the user types and are refined when the API confirms the scheme. Accepts true to show scheme and additional scheme icons, or an object for granular control which accepts:

• scheme: (boolean) show detected scheme
• additionalSchemes: (boolean) show co-branded icons
• placeholders: (boolean) show Visa/Mastercard/Amex before detection

A maximum of 3 icons are shown — ensure the input is wide enough to accommodate them. Only available on addCardNumberField.

版本与发布记录

@gr4vy/secure-fields 共发布 99 个版本,首次发布于 2022/08/13;过去 12 个月发布了 33 个版本。

版本发布日期距今
2.13.0latest2026/11/0313 天前
2.12.02026/11/0313 天前
2.11.22026/10/051 个月前
2.11.2--canary.1346.7573de9.0canary2026/10/051 个月前
2.11.2--canary.1339.789d550.02026/09/301 个月前
2.11.12026/09/251 个月前

关于 @gr4vy/secure-fields 的常见问题

@gr4vy/secure-fields 是什么?

Gr4vy-hosted secure fields offering advanced theming, PCI compliance, event handling, and more.

如何安装 @gr4vy/secure-fields?

在项目目录运行 npm install @gr4vy/secure-fields,或使用 pnpm add / yarn add / bun add。

@gr4vy/secure-fields 支持 TypeScript 吗?

支持。包内自带 TypeScript 类型声明(package.json 声明了 types 入口),安装后即可获得类型提示,无需再安装 @types 包。

@gr4vy/secure-fields 支持 ESM 还是 CommonJS?

同时提供 ES Module 与 CommonJS 入口,import 和 require() 都可以使用,打包工具会自动选择合适的版本。

@gr4vy/secure-fields 可以商用吗?

@gr4vy/secure-fields 使用 MIT 许可。宽松许可:允许商业使用、修改和再分发,通常只需在分发时保留原版权与许可声明。以上为概括,不构成法律意见,请以许可原文为准。

@gr4vy/secure-fields 的下载量有多少?

根据 npm 官方下载统计,@gr4vy/secure-fields 在 2026/10/17 – 2026/11/15 这 30 天内被下载 51,826 次,日均约 1,728 次。下载量会把 CI 构建、镜像同步和作为其他包依赖的安装一并计入,适合横向比较热度,不能直接等同于使用人数。

@gr4vy/secure-fields 还在维护吗?

最新版本 2.13.0 发布于 2026/11/03(13 天前);至今共发布 99 个版本,其中过去 12 个月发布了 33 个;首次发布于 2022/08/13。发布频率只是参考信号:功能稳定的工具可能很少需要更新,建议结合源码仓库的 issue 和提交记录判断。