This isn’t a false positive, but rather a case where the advisory has been updated to include earlier versions of the `time` crate.
Unfortunately the fix is only in `time` v0.2, and it’s unclear if it can be backported to v0.1 due to API constraints.