devtrackers.gg
This is because of a weird combination of factors. The up-to-date value ranges of that mod are (31-40) for % increased Damage with Bleeding, and 25 (with no range) for chance to cause Bleeding on hit with Attacks.
You have an item generated with an older version of the mod, which had a lower value of the first stat (hence why that item's current value of 29 is outside the range), and a value of 0 in the second stat (chance to inflict bleeding), because the mod didn't originally have that stat, so had no value for it.
So it should be showing that line as "Attacks have 0(25)% chance to cause Bleeding", showing the current value (0) and the valid range (25) of values - what it would re-roll to if you used a divine orb.
However, the chance to inflict bleeding stat is described as "Attacks have x% chance to cause Bleeding" only for cases where x is in the range 1-99, and described as "Attacks cause Bleeding" otherwise - because in general use the "otherwise" case is only for values of 100 (or higher). Stats aren't described when the value is zero, because they don't do anything then. But because this case trying to show the range as well means it does describe the stat while its current value is zero, it uses the wrong line, and because that line doesn't display the value, it has no-where to show the 0, or include the valid value range (25).
If you use a divine orb on the item, it will reroll both stats to within the current valid range with the mod - so the increased damage will go up from 29 to something in the range (31-40), and the chance to inflict bleeding will go up from 0 to 25.