Bump toml from 4.1.2 to 5.0.0

[dependabot]

Bumps toml from 4.1.2 to 5.0.0.

Changelog

Sourced from toml's changelog.

5.0.0 - July 14 2026

• Breaking: Integers outside JavaScript's safe range (beyond ±Number.MAX_SAFE_INTEGER) now throw a parse error instead of silently returning a rounded value (#28). Opt in to lossless handling of the full 64-bit range with toml.parse(input, { bigint: true }), which returns all integer values as BigInt.
• Breaking: Integers outside TOML's 64-bit signed integer range now throw a parse error in either mode, as required by the spec. Previously they were silently rounded.

4.3.0 - July 13 2026

• Add opt-in Temporal support via toml.parse(input, { useTemporal: true }), mapping offset date-times to Temporal.ZonedDateTime and local date-times/dates/times to Temporal.PlainDateTime/PlainDate/PlainTime. An implementation can be supplied via the temporal option on runtimes without a Temporal global. (#69)

4.2.0 - July 13 2026

• Address security advisory GHSA-82x6-q7mm-w9cf (CVE pending), in which deeply nested arrays or inline tables could overflow the call stack and crash the process with an uncatchable RangeError. Nesting is now bounded (default 500 levels), and input past the limit throws a normal parse error. The limit is configurable via toml.parse(input, { maxDepth }).

Commits

• ccd8b10 5.0.0
• 00ac4a6 Update changelog
• 121e5fa Merge pull request #74 from BinaryMuse/mkt/big-ints
• 2b6bcb7 Add opt-in BigInt support, throw when parsing out of bounds values
• 38fb4e6 4.3.0
• 5222a64 feat: Add opt-in Temporal support for date/time values (#73)
• 95f79b3 4.2.0
• b71c439 Merge pull request #72 from BinaryMuse/fix/nesting-depth-dos
• a2d6dbb Update changelog
• 967b8b0 fix: bound nesting depth to prevent stack-overflow DoS
• Additional commits viewable in compare view

[psiinon]

Checkmarx One – Scan Summary & Details – 1c4adb5a-c2f0-42e7-abc4-9ee498e78dfe

Great job! No new security vulnerabilities introduced in this pull request

---

Communicate with Checkmarx by submitting a PR comment with @Checkmarx followed by one of the supported commands. Learn about the supported commands here.