For simplicity, and since 1.0.0 was released in 2013 I'd recommend going ahead and baselining against 1.0 and renaming the module to druid-1.0

@trask done, thank you

@trask assertInverse.set(true) will make muzzle3 check failed ,history check

I think your best option is to set the version range back to versions.set("[0.2.6,)") so you could add assertInverse.set(true). The same approach is used in

@laurit Early versions may not have the DruidDataSourceStatManager.addDataSource method, or the parameters may be different, such as
0.2
0.2.5

Can I write in this way

muzzle {
  pass {
    group.set("com.alibaba")
    module.set("druid")
    versions.set("[0.1.18,)")
    skip("1.0.30")
    assertInverse.set(true)
  }
}

@AlchemyDing sure, I think you can also use versions.set("(,)") if muzzle passes on all published versions.

@laurit done, thank you