ExtendScript is Adobe's extended implementation of JavaScript. It was developed as a common scripting technology for Adobe applications and provides access to the FrameMaker object model. Through this object model, a script can interact with documents, books, paragraphs, text ranges, markers, cross-references, variables, tables, graphics, and many other FrameMaker objects. Because ExtendScript is based on JavaScript, developers familiar with JavaScript will find much of its syntax immediately recognizable.
While ExtendScript has been deprecated for the Creative Cloud applications, it is still very useful for scripting FrameMaker.
FrameScript, by comparison, is a scripting and automation environment developed specifically for FrameMaker. Rather than being a general Adobe scripting language, it was designed around FrameMaker and document-production workflows. Its language and commands therefore tend to reflect FrameMaker concepts directly. FrameScript has a long history in the FrameMaker community and has been used to build everything from small productivity utilities to sophisticated document-processing and publishing solutions. At the time writing this, it seem FrameScript is not being actively developed or supported. Whether support and development is going to come back, seems a little unclear, unfortunately
The principal difference between the two is therefore their background and approach. ExtendScript comes from the broader Adobe ecosystem and exposes FrameMaker through a JavaScript-based object model. FrameScript approaches automation from the opposite direction: it is a specialized scripting environment centered on FrameMaker itself.
Despite these differences, their purpose is very similar. Both allow developers to turn repetitive manual procedures into repeatable processes, enforce documentation rules, manipulate large numbers of documents, create custom tools, and build workflows that would be difficult or impractical to perform manually.
This is where scripting becomes particularly valuable. A task that requires hundreds of mouse clicks across a large FrameMaker book can potentially be reduced to a single command—and, just as importantly, the script can perform that task consistently every time.
Script or Plugin?
We can extend FrameMakers capabilities with scripts and plugins, but they are not quite the same.
Active script/plugin developers
https://frameexpert.com/ This is a company led by Rick Quatro, who is also a very active and helpful supporter on the FrameMaker Forum.
Frameexpert has a shop with a fine selection of very useful extend scripts which may be found here. I am using some of these tools almost daily. "ArchiveES", for instance, is a phenomenal script for packing and moving FrameMaker projects. At the click of a button, it will collect an entire FrameMaker book with all documents and links and make a copy in a designated folder. Within this folder is a folder for graphics and insets and the FrameMaker book + documents.
4xScripts
4xScripts creates add-ons for the efficient handling of Adobe FrameMaker. They work with modularization and publication concepts, as well as media-oriented implementation. They offer programming of individual FrameMaker scripts, development and licensing of FrameMaker+XML applications, consulting, training, and support.
http://www.weststreetconsulting.com/
Daube
https://www.daube.ch/docu/fmaker64.html