Have you given any thought to adding some security to go along with library versioning? I'm thinking of something like the C# repository, where the version of the library you compile against has a digital signature, and the signature is embedded in the app. The point is to prevent an attack where someone substitutes another library, with the same version information and public interface, and hijacks your code.

I haven't thought about it, but my guess is that in the absence of any other security infrastructure it wouldn't be of much use. Could you outline some scenarios in which you think this would be helpful? Cheers, Simon