Bump card-validator from 8.1.1 to 10.0.4

[dependabot]

Bumps card-validator from 8.1.1 to 10.0.4.

Changelog

Sourced from card-validator's changelog.

10.0.4

• Update credit-card-type to 10.1.0
• Update dev dependencies
  • @​types/jest to 30.0.0
  • @​types/node to 25.0.3
  • eslint to 8.57.1
  • eslint-plugin-prettier to 5.5.4
  • jest to 30.2.0
  • jest-environment-jsdom to 30.2.0
  • prettier to 3.7.4
  • ts-jest to 29.4.6
  • typescript to 5.9.3
• Update Node to v24

10.0.3

• Updating postal code input to consider strings of length 2 to be valid input to support UK postal code format XX XXX.

10.0.2

• Update credit-card-type to 10.0.2

10.0.1

• Update (sub-) dependencies
  • babel packages to 7.0.6
  • micromatch to 4.0.6
  • semver to 6.3.1

10.0.0

• Update postal code validation to:
  • strip trailing and leading whitespace
  • verify postal code is at least 3 characters
  • confirm 1st three characters are alphanumeric
• Update braces to 3.0.3

9.1.0

• Support skipping of luhn check digit validation in card number validator.

9.0.0

• BREAKING CHANGES
  • Update node to v18
• DevDependency Updates:
  • Update prettier to v3
  • Update eslint-plugin-prettier to v5

Commits

• 1334941 10.0.4
• 2b7890e update changelog
• 021630a update changelog
• 0184767 Merge pull request #152 from braintree/update-deps
• 959a985 Merge branch 'main' into update-deps
• 6c3767e run prettier
• fdabcb0 update a lot of dependencies
• 3cb85e7 Merge pull request #151 from braintree/github-templates
• bc85954 move to new github templates format
• 4e353bd Merge pull request #147 from braintree/addSecScans
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2d56aaf

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​types/​jsdom@​21.1.6
	@​types/​react-dom@​18.2.17
	@​react-navigation/​bottom-tabs@​7.2.1
	@​react-navigation/​native@​7.0.15
	@​types/​applepayjs@​14.0.9
	@​web-std/​file@​1.1.0
	@​types/​googlepay@​0.7.10
	@​types/​jest@​28.1.8
	@​types/​react@​18.3.18
	del-cli@​5.1.0
	crc-32@​1.2.2
	@​types/​node@​24.10.10
	credit-card-type@​9.1.0
	card-validator@​10.0.4
	concurrently@​8.2.2
	@​vitejs/​plugin-basic-ssl@​2.1.4
	@​rollup/​plugin-node-resolve@​16.0.0
	@​rollup/​plugin-typescript@​12.1.2
	asn1js@​3.0.6
	asn1js@​3.0.7
	@​swc/​core@​1.4.11
	@​vitejs/​plugin-react@​4.7.0
	@​peculiar/​webcrypto@​1.5.0
	@​testing-library/​react-native@​13.2.0
	@​playwright/​test@​1.57.0

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @react-native/debugger-frontend is 96.0% likely obfuscated Confidence: 0.96 Location: Package overview From: pnpm-lock.yaml → npm/@react-native/debugger-frontend@0.76.9 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@react-native/debugger-frontend@0.76.9. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm caniuse-lite under CC-BY-4.0 License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (npm metadata) License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (package/package.json) License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (package/LICENSE) From: pnpm-lock.yaml → npm/@babel/core@7.29.0 → npm/caniuse-lite@1.0.30001695 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/caniuse-lite@1.0.30001695. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		License policy violation: npm caniuse-lite under CC-BY-4.0 License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (npm metadata) License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (package/package.json) License: CC-BY-4.0 - The applicable license policy does not permit this license (5) (package/LICENSE) From: pnpm-lock.yaml → npm/caniuse-lite@1.0.30001791 ℹ Read more on: This package | This alert | What is a license policy violation? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/caniuse-lite@1.0.30001791. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[matt-evervault]

Dependabot PR Review: card-validator 8.1.1 → 10.0.4

Summary

Safe to merge. No code changes were required — the build passes cleanly with the new lockfile.

Usage in this codebase

The npm card-validator package is used in only two files, both in @evervault/inputs:

• packages/inputs/src/app/EvervaultCard.ts
  • cardValidator.number(cardNumber) — uses isValid / isPotentiallyValid
  • cardValidator.expirationDate(cardExpiry) — uses isValid / isPotentiallyValid (mutates isPotentiallyValid locally)
  • cardValidator.cvv(cardCVV, cvvLength) — uses isValid / isPotentiallyValid
• packages/inputs/src/app/InputElementsManager.ts
  • cardValidator.number(number).card?.type — used to drive iMask card-number masks (american-express, unionpay)

Note: The internal package @evervault/card-validator (under packages/card-validator/) does not depend on the npm card-validator; it implements validation independently. So the only consumers of the upstream change are the two files above.

Changelog review (8.1.1 → 10.0.4)

card-validator

• v9.0.0 (breaking): Node ≥ 18 minimum + dev-dep updates only — no public API changes
• v9.1.0: Optional luhn-skip support (additive, opt-in) — not used here
• v10.0.0 (breaking): Postal code validation rewrite — not used here
• v10.0.1: Sub-deps (babel, micromatch, semver)
• v10.0.2 / v10.0.4: bumps credit-card-type (9.1.0 → 10.1.2)
• v10.0.3: Postal code 2-char support — not used here
• v10.0.4: Node updated to v24

credit-card-type (transitive, 9.1.0 → 10.1.2)

• v10.0.0 (breaking): Node ≥ 18 minimum
• v10.1.0: Added Verve card type (additive)

The signatures and return shapes of number(), expirationDate(), and cvv() (specifically the isValid, isPotentiallyValid, card.type, month, year fields we read) are unchanged across this range. The only breaking changes affect postal-code validation (not used) and Node minimum version (the inputs package already declares engines.node: "^24").

Security / performance

• Picked up sub-dep updates in v10.0.1 (braces → 3.0.3, micromatch → 4.0.6, semver → 6.3.1) which include known vuln fixes — directional improvement.
• New Verve card type from credit-card-type 10.1.0 only adds an additional brand to detection; the iMask fallback in InputElementsManager.ts already defaults to the standard 16-digit mask if a brand isn't matched, so unknown new brands degrade gracefully.
• No suspicious changes observed in the version range.

Verification performed

• pnpm install --frozen-lockfile — clean install
• pnpm build — all packages build successfully (browser, inputs, react, js, ui-components, 3ds, etc.)
• pnpm --filter "@evervault/inputs..." typecheck — passes

Changes pushed

None. Build and typecheck pass against the dependabot lockfile as-is, so no follow-up commits were needed on this branch.

---

Generated by Claude Code