Looks like RivescriptJS no longer maintained...

[I-am-Orion]

I notice, no issue has been solved for the past few months...including my issue...

[dcsan]

the repo is active, these are closed issues:
https://github.com/aichaos/rivescript-js/issues?q=is%3Aissue+is%3Aclosed

[kirsle]

If others want to step up and help maintain this repo, get in touch with me and I can see about adding write access for them. I have other priorities nowadays and don't have as much time to be the sole maintainer of this repo. Pull requests are accepted but bug reports that I'm expected to fix myself will be done whenever I have the time and gumption to dive into the codebase once again.

At this stage of the game I consider the RiveScript language spec v2 to be "feature complete" and am only interested in bug fixes and performance optimizations. There's plenty of room for improvement here (for example, ! sub substitutions could be optimized to support massive numbers of substitutions, i.e. to translate all Emoji symbols into text versions, and the current algorithm iterates over them as a list and doesn't scale well for large numbers of substitutions).

So I'd ask prospective maintainers to understand the RiveScript Goals and Scope and to keep feature parity as much as possible between all the implementations of RiveScript: if you wrote a bot using rivescript-js you should be able to take all your .rive files and run them as-is in the Python, Go, Java or Perl versions without needing to modify them: the same feature set should work more or less the same on all these environments (object macro language support excluded). For example, I don't want to see rivescript-js go off on its own tangent and support large extensions to the language unless the maintainer also commits to extending the Go, Python and Java versions (at minimum) to follow these new feature developments. If you'd like to take RiveScript in a new direction, fork the project and name it something else as SuperScript.js did.