Skip to content
Flint
Blog

valueSafety

Reports JSON values that are unsafe for data interchange.

✅ This rule is included in the json logical and logicalStrict presets.

JSON is widely used for data interchange between systems, but certain values can cause interoperability issues when transferred between different parsers and environments. This rule detects values that are unsafe for interchange, preventing data corruption, silent failures, or inconsistent behavior across different platforms and languages.

Unsafe Values

Section titled “Unsafe Values”

This rule detects the following unsafe values:

  • Lone surrogates in strings: Incomplete Unicode character pairs that can cause encoding/decoding failures
  • Numbers that evaluate to Infinity: Values like 1e400 that exceed JavaScript’s number range
  • Unintentional zeros: Very small numbers (e.g., 1e-400) that silently evaluate to zero due to precision limitations
  • Unsafe integers: Numbers outside JavaScript’s safe integer range (±2^53-1) that lose precision
  • Subnormal numbers: Very small floating point values that may be handled differently across systems

Examples

Section titled “Examples”
5<3[sp ansty="le--0:#F78C6C;--1:#AA09">822e3<08sp ansty="le--0:#D6DEEB;--1:#403F">5<3]d ivclassNa="meco"><8]d>5<3{d ivclassNa="meec-li">nt< sp ansty="le--0:#7FDBCA;--1:#096E">72"valu53<: sp ansty="le--0:#D9F5DD;--1:#1111">1<1"sp ansty="le--0:#F78C6C;--1:#AA09">82\ud8<3dsp ansty="le--0:#D9F5DD;--1:#1111">1<1"d ivclassNa="meec-li">5<3}d ivclassNa="meco"><}d>5<3[sp ansty="le--0:#F78C6C;--1:#AA09">821e-4<00sp ansty="le--0:#D6DEEB;--1:#403F">5<3]d ivclassNa="meco"><0]d>5<3{d ivclassNa="meec-li">nt< sp ansty="le--0:#7FDBCA;--1:#096E">72"i53<: sp ansty="le--0:#F78C6C;--1:#AA09">8290071992547409<92d ivclassNa="meec-li">5<3}d ivclassNa="meco"><}d>5<3[sp ansty="le--0:#F78C6C;--1:#AA09">822.2250738585072009e-3<08sp ansty="le--0:#D6DEEB;--1:#403F">5<3]d ivclassNa="meco"><8]d>
3098<2123 spans="tyle--0:#D6DEEB;--1:#40">3F<53, spans="tyle--0:#F78C6C;--1:#AA">0982<1234 spans="tyle--0:#D6DEEB;--1:#40">3F<53, spans="tyle--0:#F78C6C;--1:#AA">09821<2345 spans="tyle--0:#D6DEEB;--1:#40">3<345><]di vdivclass="Nameexpressive-">3de6E72"em3F<53: spans="tyle--0:#D9F5DD;--1:#11">1<111" spans="tyle--0:#C789D6;--1:#7C">56<86 🔥spa="nstyle--0:#D9F5DD;--1:#">1<111 11"divcla="ssNamee">4<03F 53}divcla="ssNa"><"><🔥" }divdivc="lassNameexpress"><-contentfi gcaptionc="lassNa">:<#40 3F53{divc="lassNam">me:#096E7<2"em oji"s="panstyle--0:#D6DEEB;--1">:#<403F 53: s="panstyle--0:#D9F5DD;--1">:<#111 111"s="panstyle--0:#F78C6C;--1">:#AA0982\ud8<3d\u dd25s="panstyle--0:#D9F5DD;--1">:<#11 1111"divc="lassNam">:<#40 3F53}divc="lass"><25" }divdivc="lassNameexpress"><-contentfi gcaptionc="lassNa">:<#403 F53[s="panstyle--0:#F78C6C;--1">:<#AA0 9820s="panstyle--0:#D6DEEB;--1">:#<403F 53, s="panstyle--0:#F78C6C;--1">:#A:#<403F 53, s="panstyle--0:#F78C6C;--1">:<#AA0 9820s="panstyle--0:#D6DEEB;--1">:<#40 3F53]divc="lass">< 0.><0, 0]divdivc="lassNameexpress"><-contentfi gcaptionc="lassNa">:<#40 3F53{divc="lassNam">me:#09<6E72 "id"s="panstyle--0:#D6DEEB;--1">:#<403F 53: s="panstyle--0:#F78C6C;--1">:#AA098290071992<547 40991divc="lassNam">:<#40 3F53}divc="lass"><740>

When Not To Use It

Section titled “When Not To Use It”

If your project intentionally uses a mix of JSON levels of safety, such as systems that manually manipulate strings, this rule might not reflect your project’s needs. Consider refactoring to use safer value representations.

Further Reading

Section titled “Further Reading”

Equivalents in Other Linters

Section titled “Equivalents in Other Linters”