For security, scripts are necessarily peer-reviewed, audited, and then a copy is archived at the KES repository as a given version at a single point in time. (Roughly speaking, think of it as a stable OS release with certain approved package versions versus a rolling release.) They aren't in lock-step with the bleeding-edge version of the remote scripts, and contain the pared down functionality from those scripts in order to integrate it with KES.
It's the responsibility of script authors to submit updates, or the KES maintainers (usually the latter) to make changes to said scripts. (Again, this is no different from the OS/package maintainer analogy above.) When KES releases a version update at certain intervals, it includes approved changes or updates to the collection of scripts therein. Remote scripts are not updated over the air continuously.
Scripts are generally slow-moving once core functionality is in place, and KES encourages atomic scripts that add small, synergistic features that do one thing well, so I don't see version drift being problematic. Hope that answers your question.
Add comment