Bump swagger-typescript-api from 13.1.3 to 13.12.2

[dependabot]

Bumps swagger-typescript-api from 13.1.3 to 13.12.2.

Release notes

Sourced from swagger-typescript-api's releases.

v13.12.2

Patch Changes

• #1779 306d59a Thanks @​js2me! - Fix code injection via unescaped enum string values in generated TypeScript enums

  Malicious OpenAPI specs could embed arbitrary JavaScript in components.schemas.*.enum string values. Ts.StringValue wrapped values in double quotes without escaping, allowing attackers to break out of generated enum declarations and inject code that executes at module load when consumers import the generated client. Enum string values are now properly escaped.

  Reported by @​thegr1ffyn: GHSA-5f94-x226-ccpm.

• #1779 306d59a Thanks @​js2me! - Fix code injection via unescaped servers[0].url in generated axios and fetch HTTP clients

  Malicious OpenAPI specs could embed arbitrary JavaScript in servers[0].url. The value was interpolated raw into string literals in generated client constructors, allowing computed-property-key injection and arbitrary code execution when consumers instantiated HttpClient or Api (axios) or imported the generated module (fetch). apiConfig.baseUrl is now escaped once at the source before template rendering.

  Reported by @​thegr1ffyn: GHSA-38c3-wv3c-v3xj (axios), GHSA-hqj5-cw9f-rx67 (fetch).

• #1779 306d59a Thanks @​js2me! - Fix code injection via unescaped OpenAPI path strings in generated method bodies

  Malicious OpenAPI specs could embed arbitrary JavaScript in path keys. Values were interpolated raw into template literals in generated API methods, so ${…} expressions ran with full process privileges on every call to the affected method. Route paths are now escaped for template-literal insertion while preserving deliberate ${paramName} interpolations for declared path parameters.

  Reported by @​thegr1ffyn: GHSA-w284-33mx-6g9v.

• #1779 306d59a Thanks @​js2me! - Fix authorization-token exfiltration and SSRF via spec $ref during remote schema resolution

  When generating from a remote OpenAPI spec, the generator walked every external $ref and fetched any http(s):// URL without validating the target. A malicious spec could force HTTP requests to loopback, RFC-1918, link-local (including cloud metadata at 169.254.169.254), or internal hostnames reachable from the generator process. Redirect chains were also followed without re-validation.

  Remote schema fetches now enforce a defense-in-depth policy:

  • Block private, link-local, and loopback addresses (IPv4 and IPv6), including localhost
  • Allow cross-origin fetches only to public hosts; same-origin $ref targets remain allowed
  • Allow the explicit --url spec source even on loopback (local development)
  • Follow redirects manually (max 5) and re-validate each hop
  • Forward authorizationToken only to same-origin remote URLs, not cross-origin $ref targets

  Reported by @​thegr1ffyn: GHSA-h754-fxp7-88wx, GHSA-x36r-4347-pm5x.

v13.12.1

Patch Changes

• caa2874 Thanks @​js2me! - update all deps to latest (patch + minor deps, no major updates)

v13.12.0

Minor Changes

• 691559a Thanks @​js2me! - Add enumStyle: "const-enum" to generate TypeScript const enum declarations for schema enums and the built-in ContentType.

v13.11.2

Patch Changes

• 691d07d Thanks @​js2me! - Fix schema type name resolution when preferExistingSchemaNamesForExternalRefs is false

... (truncated)

Changelog

Sourced from swagger-typescript-api's changelog.

13.12.2

Patch Changes

• #1779 306d59a Thanks @​js2me! - Fix code injection via unescaped enum string values in generated TypeScript enums

  Malicious OpenAPI specs could embed arbitrary JavaScript in components.schemas.*.enum string values. Ts.StringValue wrapped values in double quotes without escaping, allowing attackers to break out of generated enum declarations and inject code that executes at module load when consumers import the generated client. Enum string values are now properly escaped.

  Reported by @​thegr1ffyn: GHSA-5f94-x226-ccpm.

• #1779 306d59a Thanks @​js2me! - Fix code injection via unescaped servers[0].url in generated axios and fetch HTTP clients

  Malicious OpenAPI specs could embed arbitrary JavaScript in servers[0].url. The value was interpolated raw into string literals in generated client constructors, allowing computed-property-key injection and arbitrary code execution when consumers instantiated HttpClient or Api (axios) or imported the generated module (fetch). apiConfig.baseUrl is now escaped once at the source before template rendering.

  Reported by @​thegr1ffyn: GHSA-38c3-wv3c-v3xj (axios), GHSA-hqj5-cw9f-rx67 (fetch).

• #1779 306d59a Thanks @​js2me! - Fix code injection via unescaped OpenAPI path strings in generated method bodies

  Malicious OpenAPI specs could embed arbitrary JavaScript in path keys. Values were interpolated raw into template literals in generated API methods, so ${…} expressions ran with full process privileges on every call to the affected method. Route paths are now escaped for template-literal insertion while preserving deliberate ${paramName} interpolations for declared path parameters.

  Reported by @​thegr1ffyn: GHSA-w284-33mx-6g9v.

• #1779 306d59a Thanks @​js2me! - Fix authorization-token exfiltration and SSRF via spec $ref during remote schema resolution

  When generating from a remote OpenAPI spec, the generator walked every external $ref and fetched any http(s):// URL without validating the target. A malicious spec could force HTTP requests to loopback, RFC-1918, link-local (including cloud metadata at 169.254.169.254), or internal hostnames reachable from the generator process. Redirect chains were also followed without re-validation.

  Remote schema fetches now enforce a defense-in-depth policy:

  • Block private, link-local, and loopback addresses (IPv4 and IPv6), including localhost
  • Allow cross-origin fetches only to public hosts; same-origin $ref targets remain allowed
  • Allow the explicit --url spec source even on loopback (local development)
  • Follow redirects manually (max 5) and re-validate each hop
  • Forward authorizationToken only to same-origin remote URLs, not cross-origin $ref targets

  Reported by @​thegr1ffyn: GHSA-h754-fxp7-88wx, GHSA-x36r-4347-pm5x.

13.12.1

Patch Changes

• caa2874 Thanks @​js2me! - update all deps to latest (patch + minor deps, no major updates)

13.12.0

Minor Changes

• 691559a Thanks @​js2me! - Add enumStyle: "const-enum" to generate TypeScript const enum declarations for schema enums and the built-in ContentType.

13.11.2

... (truncated)

Commits

• cc3e4d1 Version Packages (#1780)
• 306d59a Security/fixing vulnerabilities (#1779)
• de76b58 test: add yaml url fetch test
• ee5034b Version Packages (#1774)
• c73d6bc Add unrun as devDependency for tsdown 0.22.x compatibility
• caa2874 chore: update deps
• ddf2943 Version Packages (#1769)
• 691559a feat: add const-enum enumStyle
• febb2d8 Version Packages (#1768)
• 691d07d Add changeset for preferExistingSchemaNamesForExternalRefs false-case fix
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for swagger-typescript-api since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.