One of the problems with osaxen placed in ~/Library/Scripting Additions/, /Library/Scripting Additions/, or /System/Library/Scripting Additions/ is that they are always active. This means that in the attempt to write and debug a plain vanilla AppleScript (PVAS, or PeeVas in my mind) you may inadvertently be using a term from one of the osaxen, or trickier yet, a coercion from one of them. You have no way of knowing that, but your script will nonetheless break on someone else’s machine if they don’t have that osax. Further, you have no way of knowing if a failure using one of them is caused by the presence of another, since they aren’t guaranteed not to conflict.
Bearing all this in mind, I just started a script to zip mine in place (rather than move them), and using a script by Kai, unzipping them and removing the zipped version (which isn’t removed by the unzip) - a kind of osax Conflict Catcher. As I begin, however, it occurs to me that I can’t have been the first to worry about this, so there certainly must exist a script for doing this in this community.
Care to share or comment?