why are we deprecating cuid, there are case one may want to use k-sortable ids, And the security issue is dependent on your use-case, there are cases where you might even need to use the int auto increment as an id, it might be bad for some scenarios but you still may want to use it for your use-case.
It is not a bug it is a feature !!
you could just mention the security issue of using k-sortable ids with out deprecating it,
marking it as a security issue implies that the package or id have other security issues when the issue actually is not unique to cuid, but common to all sortable ids, provide the info and let the people pick what they want to use
why are we deprecating cuid, there are case one may want to use k-sortable ids, And the security issue is dependent on your use-case, there are cases where you might even need to use the int auto increment as an id, it might be bad for some scenarios but you still may want to use it for your use-case. It is not a bug it is a feature !! you could just mention the security issue of using k-sortable ids with out deprecating it, marking it as a security issue implies that the package or id have other security issues when the issue actually is not unique to cuid, but common to all sortable ids, provide the info and let the people pick what they want to use