chore(deps): bump ttsc from 0.12.4 to 0.13.1

[dependabot]

Bumps ttsc from 0.12.4 to 0.13.1.

Release notes

Sourced from ttsc's releases.

v0.13.1

   🚀 Features

• benchmark:
  • --checkers 2/4/8 threading spectrum (replace single/multi binary)  -  by @​samchon and Claude Opus 4.7 (1M context) in samchon/ttsc#128 (1b568)
  • Measure lint sidecar timings  -  by @​samchon (dc0a8)
  • Refresh lint timing dashboard  -  by @​samchon (011de)

   🐞 Bug Fixes

• benchmark:
  • Keep fixture worktrees clean  -  by @​samchon (16dfd)
  • Align lint scope and timing  -  by @​samchon (ec64b)
  • Pin tsgo label from lockfile  -  by @​samchon (6be1a)
  • Pin fixture tsgo runtime  -  by @​samchon (cb834)
  • Scrub tarball refs before tsgo pin  -  by @​samchon (c0c9c)
  • Format generated prisma setup  -  by @​samchon (b604c)
• ttsc:
  • Honor disabled diagnostics timing  -  by @​samchon (91751)
• website:
  • Clarify benchmark headline metrics  -  by @​samchon (84c21)

    View changes on GitHub

v0.13.0

   🚀 Features

• bench:
  • Format threading benchmark restore + @​ttsc/lint files-scope format guard  -  by @​samchon and Claude Opus 4.7 (1M context) in samchon/ttsc#124 (f764f)
• cli:
  • Forward tsgo flags through ttsc and ttsx  -  by @​samchon and Claude Opus 4.7 (1M context) in samchon/ttsc#113 (d1562)
• lint:
  • Performance optimization reducing fixed costs.  -  by @​samchon and Claude Opus 4.7 (1M context) in samchon/ttsc#122 (b84c7)
  • Parallelize Engine.Run, restore dashboard stacks, add Format benchmark category  -  by @​samchon and Claude Opus 4.7 (1M context) in samchon/ttsc#123 (15fc8)
• test:
  • Add nestia compatibility workflow  -  by @​samchon and Claude Opus 4.7 (1M context) in samchon/ttsc#106 (28039)
• website:
  • Performance benchmark and a little bit optimizations  -  by @​samchon and Claude Opus 4.7 (1M context) in samchon/ttsc#114 (786ea)
  • Refreshed benchmark.json  -  by @​samchon and Claude Opus 4.7 (1M context) in samchon/ttsc#126 (cd0f0)

   🐞 Bug Fixes

• lint: Withdraw ESLint config support, repair the formatter, and move plugin options to config files  -  by @​samchon and Claude Opus 4.7 (1M context) in samchon/ttsc#104 (50d86)
• ttsc: Rewrite TS extension imports for emit  -  by @​resolvicomai and Copilot Autofix powered by AI in samchon/ttsc#105 (69d42)

   🏎 Performance

• ttsc: Drop SingleThreaded so TypeScript-Go parses/checks/emits in parallel  -  by @​samchon and Claude Opus 4.7 (1M context) in samchon/ttsc#112 (5cc62)

    View changes on GitHub

Commits

• 2e09355 chore: release v0.13.1
• af935cf docs(benchmark): anchor lint headline to vscode
• 7c3577e Merge pull request #129 from samchon/feat/benchmark-legacy-ts6
• c8b0b39 docs(benchmark): publish refreshed lint metrics
• b604c38 fix(benchmark): format generated prisma setup
• 28e1741 benchmark is on recording
• c0c9c79 fix(benchmark): scrub tarball refs before tsgo pin
• cb8343d fix(benchmark): pin fixture tsgo runtime
• 84c21d9 fix(website): clarify benchmark headline metrics
• 9175190 fix(ttsc): honor disabled diagnostics timing
• Additional commits viewable in compare view

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)

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​ttsc@​0.12.4 ⏵ 0.13.1			+1	+1

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 @ttsc/darwin-arm64 is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/ttsc@0.13.1 → npm/@ttsc/darwin-arm64@0.13.1 ℹ 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/@ttsc/darwin-arm64@0.13.1. 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		Obfuscated code: npm @ttsc/darwin-arm64 is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/ttsc@0.13.1 → npm/@ttsc/darwin-arm64@0.13.1 ℹ 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/@ttsc/darwin-arm64@0.13.1. 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		Obfuscated code: npm @ttsc/darwin-x64 is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/ttsc@0.13.1 → npm/@ttsc/darwin-x64@0.13.1 ℹ 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/@ttsc/darwin-x64@0.13.1. 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		Obfuscated code: npm @ttsc/darwin-x64 is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/ttsc@0.13.1 → npm/@ttsc/darwin-x64@0.13.1 ℹ 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/@ttsc/darwin-x64@0.13.1. 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		Obfuscated code: npm @ttsc/linux-arm64 is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/ttsc@0.13.1 → npm/@ttsc/linux-arm64@0.13.1 ℹ 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/@ttsc/linux-arm64@0.13.1. 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		Obfuscated code: npm @ttsc/linux-arm64 is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/ttsc@0.13.1 → npm/@ttsc/linux-arm64@0.13.1 ℹ 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/@ttsc/linux-arm64@0.13.1. 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		Obfuscated code: npm @ttsc/linux-x64 is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/ttsc@0.13.1 → npm/@ttsc/linux-x64@0.13.1 ℹ 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/@ttsc/linux-x64@0.13.1. 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		Obfuscated code: npm @ttsc/linux-x64 is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/ttsc@0.13.1 → npm/@ttsc/linux-x64@0.13.1 ℹ 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/@ttsc/linux-x64@0.13.1. 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		Obfuscated code: npm @ttsc/win32-arm64 is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/ttsc@0.13.1 → npm/@ttsc/win32-arm64@0.13.1 ℹ 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/@ttsc/win32-arm64@0.13.1. 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		Obfuscated code: npm @ttsc/win32-arm64 is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/ttsc@0.13.1 → npm/@ttsc/win32-arm64@0.13.1 ℹ 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/@ttsc/win32-arm64@0.13.1. 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		Obfuscated code: npm @ttsc/win32-x64 is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/ttsc@0.13.1 → npm/@ttsc/win32-x64@0.13.1 ℹ 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/@ttsc/win32-x64@0.13.1. 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		Obfuscated code: npm @ttsc/win32-x64 is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/ttsc@0.13.1 → npm/@ttsc/win32-x64@0.13.1 ℹ 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/@ttsc/win32-x64@0.13.1. 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