libraries.io Open in urlscan Pro
35.244.128.241  Public Scan

Form analysis
1 forms found in the DOM

GET /search

<form class="navbar-form search_form" action="/search" accept-charset="UTF-8" method="get">
  <div class="input-group input-group">
    <input type="text" name="q" id="q" value="" placeholder="Search Packages" class="form-control search-input" size="40">
    <span class="input-group-btn">
      <button class="btn btn-primary" type="submit">
        <i class="fa fa-search"></i>
      </button>
    </span>
  </div>
</form>

Text Content

Watch our latest webinar to understand the difference between data from
Libraries.io and the Tidelift Subscription.
Toggle navigation
 * 

 * Login
    * GitHub
    * GitLab
    * Bitbucket
    * 
    * By logging in you accept
      our terms of service
      and privacy policy


RASAHQ/RASA



--------------------------------------------------------------------------------

💬 Open source machine learning framework to automate text- and voice-based
conversations: NLU, dialogue management, connect to Slack, Facebook, and more -
Create chatbots and voice assistants

https://rasa.com/docs/rasa/

License: Apache-2.0

Language: Python

Keywords: bot, bot-framework, botkit, bots, chatbot, chatbots,
chatbots-framework, conversation-driven-development, conversational-agents,
conversational-ai, conversational-bots, machine-learning,
machine-learning-library, mitie, natural-language-processing, nlp, nlu, rasa,
spacy, wit

--------------------------------------------------------------------------------


RASA OPEN SOURCE



--------------------------------------------------------------------------------

💡 We're migrating issues to Jira 💡

Starting January 2023, issues for Rasa Open Source are located in this Jira
board. You can browse issues without being logged in; if you want to create
issues, you'll need to create a Jira account.

--------------------------------------------------------------------------------



Rasa is an open source machine learning framework to automate text and
voice-based conversations. With Rasa, you can build contextual assistants on:

 * Facebook Messenger
 * Slack
 * Google Hangouts
 * Webex Teams
 * Microsoft Bot Framework
 * Rocket.Chat
 * Mattermost
 * Telegram
 * Twilio
 * Your own custom conversational channels

or voice assistants as:

 * Alexa Skills
 * Google Home Actions

Rasa helps you build contextual assistants capable of having layered
conversations with lots of back-and-forth. In order for a human to have a
meaningful exchange with a contextual assistant, the assistant needs to be able
to use context to build on things that were previously discussed – Rasa enables
you to build assistants that can do this in a scalable way.

There's a lot more background information in this blog post.

--------------------------------------------------------------------------------

 * 🤔 Learn more about Rasa

 * 🤓 Read The Docs

 * 😁 Install Rasa

 * 🚀 Dive deeper in the learning center

 * 🤗 Contribute

 * ❓ Get enterprise-grade support

 * 🏢 Explore the features of our commercial platform

 * 📚 Learn more about research papers that leverage Rasa

--------------------------------------------------------------------------------


WHERE TO GET HELP

There is extensive documentation in the Rasa Docs. Make sure to select the
correct version so you are looking at the docs for the version you installed.

Please use Rasa Community Forum for quick answers to questions.


README CONTENTS:

 * How to contribute
 * Development Internals
 * Releases
 * License


HOW TO CONTRIBUTE

We are very happy to receive and merge your contributions into this repository!

To contribute via pull request, follow these steps:

 1. Create an issue describing the bug/improvement you want to work on or pick
    up an existing issue in Jira
 2. Follow our Pull Request guidelines: write code, test, documentation,
    changelog and follow our Code Style
 3. Create a pull request describing your changes

For more detailed instructions on how to contribute code, check out these code
contributor guidelines.

You can find more information about how to contribute to Rasa (in lots of
different ways!) on our website..

Your pull request will be reviewed by a maintainer, who will get back to you
about any necessary changes or questions. You will also be asked to sign a
Contributor License Agreement.


DEVELOPMENT INTERNALS


INSTALLING POETRY

Rasa uses Poetry for packaging and dependency management. If you want to build
it from source, you have to install Poetry first. Please follow the official
guide to see all possible options.

To update an existing poetry version to the version, currently used in rasa,
run:

    poetry self update <version>


MANAGING ENVIRONMENTS

The official Poetry guide suggests to use pyenv or any other similar tool to
easily switch between Python versions. This is how it can be done:

pyenv install 3.10.10
pyenv local 3.10.10  # Activate Python 3.10.10 for the current project

Note: If you have trouble installing a specific version of python on your system
it might be worth trying other supported versions.

By default, Poetry will try to use the currently activated Python version to
create the virtual environment for the current project automatically. You can
also create and activate a virtual environment manually — in this case, Poetry
should pick it up and use it to install the dependencies. For example:

python -m venv .venv
source .venv/bin/activate

You can make sure that the environment is picked up by executing

poetry env info


BUILDING FROM SOURCE

To install dependencies and rasa itself in editable mode execute

make install

Note for macOS users: under macOS Big Sur we've seen some compiler issues for
dependencies. Using export SYSTEM_VERSION_COMPAT=1 before the installation
helped.

INSTALLING OPTIONAL DEPENDENCIES

In order to install rasa's optional dependencies, you need to run:

make install-full

Note for macOS users: The command make install-full could result in a failure
while installing tokenizers (issue described in depth here).

In order to resolve it, you must follow these steps to install a Rust compiler:

brew install rustup
rustup-init

After initialising the Rust compiler, you should restart the console and check
its installation:

rustc --version

In case the PATH variable had not been automatically setup, run:

export PATH="$HOME/.cargo/bin:$PATH"


RUNNING AND CHANGING THE DOCUMENTATION

First of all, install all the required dependencies:

make install install-docs

After the installation has finished, you can run and view the documentation
locally using:

make livedocs

It should open a new tab with the local version of the docs in your browser; if
not, visit http://localhost:3000 in your browser. You can now change the docs
locally and the web page will automatically reload and apply your changes.


RUNNING THE TESTS

In order to run the tests, make sure that you have the development requirements
installed:

make prepare-tests-ubuntu # Only on Ubuntu and Debian based systems
make prepare-tests-macos  # Only on macOS

Then, run the tests:

make test

They can also be run at multiple jobs to save some time:

JOBS=[n] make test

Where [n] is the number of jobs desired. If omitted, [n] will be automatically
chosen by pytest.


RUNNING THE INTEGRATION TESTS

In order to run the integration tests, make sure that you have the development
requirements installed:

make prepare-tests-ubuntu # Only on Ubuntu and Debian based systems
make prepare-tests-macos  # Only on macOS

Then, you'll need to start services with the following command which uses Docker
Compose:

make run-integration-containers

Finally, you can run the integration tests like this:

make test-integration


RESOLVING MERGE CONFLICTS

Poetry doesn't include any solution that can help to resolve merge conflicts in
the lock file poetry.lock by default. However, there is a great tool called
poetry-merge-lock. Here is how you can install it:

pip install poetry-merge-lock

Just execute this command to resolve merge conflicts in poetry.lock
automatically:

poetry-merge-lock


BUILD A DOCKER IMAGE LOCALLY

In order to build a Docker image on your local machine execute the following
command:

make build-docker

The Docker image is available on your local machine as rasa:localdev.


CODE STYLE

To ensure a standardized code style we use the formatter black. To ensure our
type annotations are correct we use the type checker pytype. If your code is not
formatted properly or doesn't type check, GitHub will fail to build.

FORMATTING

If you want to automatically format your code on every commit, you can use
pre-commit. Just install it via pip install pre-commit and execute pre-commit
install in the root folder. This will add a hook to the repository, which
reformats files on every commit.

If you want to set it up manually, install black via poetry install. To reformat
files execute

make formatter


TYPE CHECKING

If you want to check types on the codebase, install mypy using poetry install.
To check the types execute

make types



DEPLOYING DOCUMENTATION UPDATES

We use Docusaurus v2 to build docs for tagged versions and for the main branch.
To run Docusaurus, install Node.js 12.x. The static site that gets built is
pushed to the documentation branch of this repo.

We host the site on netlify. On main branch builds (see
.github/workflows/documentation.yml), we push the built docs to the
documentation branch. Netlify automatically re-deploys the docs pages whenever
there is a change to that branch.


RELEASES

Rasa has implemented robust policies governing version naming, as well as
release pace for major, minor, and patch releases.

The values for a given version number (MAJOR.MINOR.PATCH) are incremented as
follows:

 * MAJOR version for incompatible API changes or other breaking changes.
 * MINOR version for functionality added in a backward compatible manner.
 * PATCH version for backward compatible bug fixes.

The following table describes the version types and their expected release
cadence:

Version Type Description Target Cadence Major For significant changes, or when
any backward-incompatible changes are introduced to the API or data model. Every
1 - 2 yrs Minor For when new backward-compatible functionality is introduced, a
minor feature is introduced, or when a set of smaller features is rolled out.
+/- Quarterly Patch For backward-compatible bug fixes that fix incorrect
behavior. As needed

While this table represents our target release frequency, we reserve the right
to modify it based on changing market conditions and technical requirements.


MAINTENANCE POLICY

Our End of Life policy defines how long a given release is considered supported,
as well as how long a release is considered to be still in active development or
maintenance.

The maintenance duration and end of life for every release are shown on our
website as part of the Product Release and Maintenance Policy.


CUTTING A MAJOR / MINOR RELEASE

A WEEK BEFORE RELEASE DAY

 1. Make sure the milestone already exists and is scheduled for the correct
    date.
 2. Take a look at the issues & PRs that are in the milestone: does it look
    about right for the release highlights we are planning to ship? Does it look
    like anything is missing? Don't worry about being aware of every PR that
    should be in, but it's useful to take a moment to evaluate what's assigned
    to the milestone.
 3. Post a message on the engineering Slack channel, letting the team know
    you'll be the one cutting the upcoming release, as well as:
    1. Providing the link to the appropriate milestone
    2. Reminding everyone to go over their issues and PRs and please assign them
       to the milestone
    3. Reminding everyone of the scheduled date for the release

A DAY BEFORE RELEASE DAY

 1. Go over the milestone and evaluate the status of any PR merging that's
    happening. Follow up with people on their bugs and fixes. If the release
    introduces new bugs or regressions that can't be fixed in time, we should
    discuss on Slack about this and take a decision on how to move forward. If
    the issue is not ready to be merged in time, we remove the issue / PR from
    the milestone and notify the PR owner and the product manager on Slack about
    it. The PR / issue owners are responsible for communicating any issues which
    might be release relevant. Postponing the release should be considered as an
    edge case scenario.

RELEASE DAY! 🚀

 1. At the start of the day, post a small message on slack announcing release
    day! Communicate you'll be handling the release, and the time you're aiming
    to start releasing (again, no later than 4pm, as issues may arise and cause
    delays). This message should be posted early in the morning and before
    moving forward with any of the steps of the release, in order to give enough
    time to people to check their PRs and issues. That way they can plan any
    remaining work. A template of the slack message can be found here. The
    release time should be communicated transparently so that others can plan
    potentially necessary steps accordingly. If there are bigger changes this
    should be communicated.
 2. Make sure the milestone is empty (everything has been either merged or moved
    to the next milestone)
 3. Once everything in the milestone is taken care of, post a small message on
    Slack communicating you are about to start the release process (in case
    anything is missing).
 4. You may now do the release by following the instructions outlined in the
    Rasa Open Source README !

AFTER A MAJOR RELEASE

After a Major release has been completed, please follow these instructions to
complete the documentation update.


STEPS TO RELEASE A NEW VERSION

Releasing a new version is quite simple, as the packages are build and
distributed by GitHub Actions.

Release steps:

 1.  Make sure all dependencies are up to date (especially Rasa SDK)
     * For Rasa SDK, except in the case of a patch release, that means first
       creating a new Rasa SDK release (make sure the version numbers between
       the new Rasa and Rasa SDK releases match)
     * Once the tag with the new Rasa SDK release is pushed and the package
       appears on pypi, the dependency in the rasa repository can be resolved
       (see below).
 2.  If this is a minor / major release: Make sure all fixes from currently
     supported minor versions have been merged from their respective release
     branches (e.g. 3.3.x) back into main.
 3.  In case of a minor release, create a new branch that corresponds to the new
     release, e.g.
     
      git checkout -b 1.2.x
      git push origin 1.2.x

 4.  Switch to the branch you want to cut the release from (main in case of a
     major, the <major>.<minor>.x branch for minors and patches)
     * Update the rasa-sdk entry in pyproject.toml with the new release version
       and run poetry update. This creates a new poetry.lock file with all
       dependencies resolved.
     * Commit the changes with git commit -am "bump rasa-sdk dependency" but do
       not push them. They will be automatically picked up by the following
       step.
 5.  If this is a major release, update the list of actively maintained versions
     in the README and in the docs.
 6.  Run make release
 7.  Create a PR against the release branch (e.g. 1.2.x)
 8.  Once your PR is merged, tag a new release (this SHOULD always happen on the
     release branch), e.g. using
     
     git checkout 1.2.x
     git pull origin 1.2.x
     git tag 1.2.0 -m "next release"
     git push origin 1.2.0 --tags
     
     GitHub will build this tag and publish the build artifacts.
 9.  After all the steps are completed and if everything goes well then we
     should see a message automatically posted in the company's Slack (product
     channel) like this one
 10. If no message appears in the channel then you can do the following checks:
     * Check the workflows in Github Actions and make sure that the merged PR of
       the current release is completed successfully. To easily find your PR you
       can use the filters event: push and branch: <version number> (example on
       release 2.4 you can see here)
     * If the workflow is not completed, then try to re run the workflow in case
       that solves the problem
     * If the problem persists, check also the log files and try to find the
       root cause of the issue
     * If you still cannot resolve the error, contact the infrastructure team by
       providing any helpful information from your investigation
 11. After the message is posted correctly in the product channel, check also in
     the product-engineering-alerts channel if there are any alerts related to
     the Rasa Open Source release like this one


CUTTING A PATCH RELEASE

Patch releases are simpler to cut, since they are meant to contain only
bugfixes.

The only things you need to do to cut a patch release are:

 1. Notify the engineering team on Slack that you are planning to cut a patch,
    in case someone has an important fix to add.
 2. Make sure the bugfix(es) are in the release branch you will use (p.e if you
    are cutting a 2.0.4 patch, you will need your fixes to be on the 2.0.x
    release branch). All patch releases must come from a .x branch!
 3. Once you're ready to release the Rasa Open Source patch, checkout the
    branch, run make release and follow the steps + get the PR merged.
 4. Once the PR is in, pull the .x branch again and push the tag!


ADDITIONAL RELEASE TASKS

Note: This is only required if the released version is the highest version
available. For instance, perform the following steps when version > version on
main.

In order to check compatibility between the new released Rasa version to the
latest version of Rasa X/Enterprise, we perform the following steps:

 1. Following a new Rasa release, an automated pull request is created in
    Rasa-X-Demo.
 2. Once the above PR is merged, follow instructions here, to release a version.
 3. Update the new version in the Rasa X/Enterprise env file. The Rasa-X-Demo
    project uses the new updated Rasa version to train and test a model which in
    turn is used by our CI to run tests in the Rasa X/Enterprise repository,
    thus validating compatibility between Rasa and Rasa X/Enterprise.


ACTIVELY MAINTAINED VERSIONS

Please refer to the Rasa Product Release and Maintenance Policy page.


LICENSE

Licensed under the Apache License, Version 2.0. Copyright 2022 Rasa Technologies
GmbH. Copy of the license.

A list of the Licenses of the dependencies of the project can be found at the
bottom of the Libraries Summary.

--------------------------------------------------------------------------------

DEPENDENCIES

Kind Requirements Latest Stable Latest Release Licenses CacheControl runtime
<0.13.0,>=0.... 0.14.0 0.14.0 Apache-2.0 Cython runtime (==0.29.28) 3.0.11
3.0.11 Apache-2.0 PyJWT runtime ~=1.7 2.9.0 2.9.0 MIT PyJWT runtime (~=1.7)
2.9.0 2.9.0 MIT PyJWT[crypto] runtime <3.0.0,>=2.0.0 SQLAlchemy runtime
<1.5.0,>=1.4.0 2.0.35 2.0.35 MIT SQLAlchemy runtime ~=1.3.0 2.0.35 2.0.35 MIT
absl-py runtime <1.5,>=0.9 2.1.0 2.1.0 Apache-2.0 absl-py runtime >=0.8.0 2.1.0
2.1.0 Apache-2.0 aio-pika runtime <8.2.4,>=6.7.1 9.4.3 9.4.3 Apache-2.0 aiogram
runtime <2.26 3.13.1 3.13.1 MIT aiohttp runtime <3.10,>=3.9.0 3.10.5 3.10.5
Apache-2.0 aiohttp runtime ~=3.5 3.10.5 3.10.5 Apache-2.0 aiokafka runtime
(==0.7.2) 0.11.0 0.11.0 Other aioredis runtime (~=1.3.1) 2.0.1 2.0.1 MIT
aioresponses runtime ~=0.6.0 0.7.6 0.7.6 MIT aioresponses extra == 'test'
(~=0.6.0) 0.7.6 0.7.6 MIT apscheduler runtime <3.10,>=3.6 3.10.4 4.0.0a5 MIT
apscheduler runtime ~=3.0 3.10.4 4.0.0a5 MIT aredis runtime (~=1.1.8) 1.1.8
1.1.8 MIT async-generator runtime ~=1.10 0.0.1 1.10 MIT/Apache-2.0 asynctest
extra == 'test' (~=0.13.0) 0.13.0 0.13.0 Apache-2.0 attrs runtime <22.2,>=19.3
24.2.0 24.2.0 MIT attrs runtime >=18 24.2.0 24.2.0 MIT boto3 runtime
<2.0.0,>=1.2... 1.35.24 1.35.24 Apache-2.0 boto3 runtime ~=1.9 1.35.24 1.35.24
Apache-2.0 certifi runtime >=2023.7.22 2024.8.30 2024.8.30 MPL-2.0 cloudpickle
runtime <2.3,>=1.2 3.0.0 3.0.0 BSD-3-Clause cloudpickle runtime ~=1.2.0 3.0.0
3.0.0 BSD-3-Clause cloudpickle runtime (~=1.2.0) 3.0.0 3.0.0 BSD-3-Clause
colorama sys_platform... <0.5.0,>=0.4.4 0.4.6 0.4.6 BSD-3-Clause colorclass
runtime <2.3,>=2.2 2.2.2 2.2.2 MIT colorclass runtime ~=2.2 2.2.2 2.2.2 MIT
coloredlogs runtime <16,>=10 15.0.1 15.0.1 MIT coloredlogs runtime ~=10.0 15.0.1
15.0.1 MIT colorhash runtime <1.3.0,>=1.0.2 2.0.0 2.0.0 MIT colorhash runtime
~=1.0 2.0.0 2.0.0 MIT confluent-kafka runtime <3.0.0,>=1.9.2 2.5.3 2.5.3
Apache-2.0 confluent-kafka runtime * 2.5.3 2.5.3 Apache-2.0 cryptography runtime
>=41.0.7 43.0.1 43.0.1 Apache-2.0/BSD-3-Clause dask python_full_... ==2022.2.0
2024.9.0 2024.9.0 BSD-3-Clause dask python_versi... ==2022.10.2 2024.9.0
2024.9.0 BSD-3-Clause dnspython runtime ==2.3.0 2.6.1 2.6.1 ISC dopamine-rl
runtime (~=3.0.0) 4.0.9 4.0.9 Apache-2.0 ecs-logging runtime (~=2.0.0) 2.2.0
2.2.0 Apache-2.0 fakeredis runtime ~=1.0 2.24.1 2.24.1 BSD-3-Clause fakeredis
extra == 'test' (~=1.4) 2.24.1 2.24.1 BSD-3-Clause fbmessenger runtime
<6.1.0,>=6.0.0 6.0.0 6.0.0 Apache-2.0 fbmessenger runtime ~=6.0 6.0.0 6.0.0
Apache-2.0 freezegun runtime ~=0.3.0 1.5.1 1.5.1 Apache-2.0 freezegun extra ==
'test' (~=0.3.0) 1.5.1 1.5.1 Apache-2.0 gast runtime ==0.2.2 0.6.0 0.6.0
BSD-3-Clause gast runtime (==0.2.2) 0.6.0 0.6.0 BSD-3-Clause gevent runtime
~=1.4 24.2.1 24.2.1 MIT github3.py extra == "gh... <3.3.0,>=3.2.0 4.0.1 4.0.1
BSD-3-Clause google-auth runtime <3 2.35.0 2.35.0 Apache-2.0 gym runtime
<=0.15.4 0.0.1 0.0.1 MIT h2 runtime (==3.0.0) 0.1.0 0.1.0 MIT h5py runtime
(~=2.10.0) 3.11.0 3.11.0 BSD-3-Clause jieba extra == "ji... <0.43,>=0.39 0.42.1
0.42.1 MIT joblib runtime <1.3.0,>=0.15.1 1.4.2 1.4.2 BSD-3-Clause json-logging
runtime (~=1.2.7) 1.3.0 1.5.0rc0 Apache-2.0 jsonpickle runtime <3.1,>=1.3 3.3.0
3.3.0 BSD-3-Clause jsonpickle runtime ~=1.1 3.3.0 3.3.0 BSD-3-Clause jsonschema
runtime <4.18,>=3.2 4.23.0 4.23.0 MIT jsonschema runtime ~=3.0 4.23.0 4.23.0 MIT
kafka-python runtime ~=1.4 2.0.2 2.0.2 Apache-2.0 matplotlib runtime <3.6,>=3.1
3.9.2 3.9.2 Other matplotlib runtime ~=3.0 3.9.2 3.9.2 Other mattermostwrapper
runtime <2.3,>=2.2 2.2 MIT mitie runtime * 0.7.36 0.7.36 MIT mitie extra ==
'mi... * 0.7.36 0.7.36 MIT mongomock runtime ~=3.18 4.1.2 4.2.0.post1 Other moto
runtime ~=1.3.8 5.0.14 5.0.15.dev19 Apache-2.0 moto extra == 'test' (~=1.3.8)
5.0.14 5.0.15.dev19 Apache-2.0 multidict runtime ==4.6.1 6.1.0 6.1.0 Apache-2.0
nbsphinx runtime >=0.3 0.9.5 0.9.5 MIT nbsphinx extra == 'test' (>=0.3) 0.9.5
0.9.5 MIT networkx runtime <2.7,>=2.4 3.2.1 3.3 BSD-3-Clause networkx runtime
~=2.4.0 3.2.1 3.3 BSD-3-Clause numpy python_versi... <1.25.0,>=1.... 2.1.1 2.1.1
Other numpy python_full_... <1.22.0,>=1.... 2.1.1 2.1.1 Other numpy
sys_platform... ==1.22.3 2.1.1 2.1.1 Other numpy runtime ~=1.16 2.1.1 2.1.1
Other packaging runtime <21.0,>=20.0 24.1 Apache-2.0/BSD-3-Clause packaging
runtime ~=19.0 24.1 Apache-2.0/BSD-3-Clause pika runtime ~=1.1.0 1.3.2 1.3.2
BSD-3-Clause pluggy runtime <2.0.0,>=1.0.0 1.5.0 1.5.0 MIT portalocker runtime
<3.0.0,>=2.7.0 2.10.1 2.10.1 BSD-3-Clause prometheus-client runtime (~=0.7.1)
0.21.0 0.21.0 Apache-2.0 prompt-toolkit runtime <3.0.29,>=3.0 3.0.47 3.0.47
BSD-3-Clause prompt-toolkit runtime <3.0 3.0.47 3.0.47 BSD-3-Clause protobuf
runtime <4.23.4,>=4.... 5.27.5 5.27.5 BSD-3-Clause psycopg2 runtime ~=2.8.2
2.9.9 2.9.9 BSD-3-Clause-Attribution psycopg2 extra == 'sql' (~=2.8.2) 2.9.9
2.9.9 BSD-3-Clause-Attribution psycopg2-binary runtime <2.10.0,>=2.8.2 2.9.9
2.9.9 BSD-3-Clause-Attribution pydantic runtime <1.10.10 2.9.2 2.9.2 MIT pydot
runtime <1.5,>=1.4 3.0.1 3.0.1 MIT pydot runtime ~=1.4 3.0.1 3.0.1 MIT
pyinstrument runtime (~=3.2.0) 4.7.3 4.7.3 BSD-3-Clause pykwalify runtime
<1.9,>=1.7 1.8.0 1.8.0 MIT pykwalify runtime ~=1.7.0 1.8.0 1.8.0 MIT
pymongo[srv,tls] runtime <4.4,>=3.8 pymongo[srv,tls] runtime ~=3.8 pytest
runtime ~=4.5 pytest extra == 'test' (~=5.0) 8.3.3 8.3.3 MIT pytest-cov runtime
~=2.7 5.0.0 5.0.0 MIT pytest-cov extra == 'test' (~=2.7) 5.0.0 5.0.0 MIT
pytest-localserver runtime ~=0.5.0 0.9.0 0.9.0 MIT pytest-localserver extra ==
'test' (~=0.5.0) 0.9.0 0.9.0 MIT pytest-sanic runtime ~=1.0.0 1.9.1 1.9.1 MIT
pytest-sanic extra == 'test' (~=1.0.0) 1.9.1 1.9.1 MIT python-dateutil runtime
<2.9,>=2.8 2.9.0 2.9.0.post0 NRL python-dateutil runtime ~=2.8 python-engineio
runtime !=5.0.0,<6,>=4 4.9.1 4.9.1 MIT python-engineio runtime >=3.9.3 4.9.1
4.9.1 MIT python-socketio runtime <6,>=4.4 5.11.4 5.11.4 MIT python-socketio
runtime >=4.3.1 5.11.4 5.11.4 MIT python-telegram-bot runtime ~=11.0 21.1.1 21.6
LGPL-3.0 pytz runtime <2023.0,>=20... 2022.7.1 2024.2 MIT pytz runtime ~=2019.1
2022.7.1 2024.2 MIT pyyaml runtime >=6.0 6.0.2 6.0.2 MIT questionary runtime
<1.11.0,>=1.5.1 2.0.1 2.0.1 MIT questionary runtime >=1.1.0 2.0.1 2.0.1 MIT
randomname runtime <0.2.0,>=0.1.5 0.2.1 0.2.1 MIT rasa-sdk runtime
<3.7.0,>=3.6.2 3.10.0 3.10.0 Apache-2.0 rasa-sdk runtime ~=1.7.0 3.10.0 3.10.0
Apache-2.0 redis runtime <5.0,>=4.5.3 5.0.8 5.0.8 MIT redis runtime ~=3.3.5
5.0.8 5.0.8 MIT redis-py-cluster runtime (==2.1.0) 2.1.3 2.1.3 MIT regex runtime
<2022.11,>=2... 2024.9.11 2024.9.11 Apache-2.0 requests runtime <3.0,>=2.23
2.32.3 2.32.3 Apache-2.0 requests runtime >=2.20 2.32.3 2.32.3 Apache-2.0
responses runtime ~=0.9.0 0.25.3 0.25.3 Apache-2.0 responses extra == 'test'
(~=0.9.0) 0.25.3 0.25.3 Apache-2.0 rocketchat-API runtime ~=0.6.0 1.32.0 1.32.0
MIT rocketchat_API runtime <1.31.0,>=0.... 1.32.0 1.32.0 MIT ruamel.yaml runtime
<0.17.22,>=0... 0.18.6 0.18.6 MIT ruamel.yaml runtime ~=0.15.0 0.18.6 0.18.6 MIT
sanic runtime <21.13,>=21.12 24.6.0 24.6.0 MIT sanic runtime ~=19.9.0 24.6.0
24.6.0 MIT sanic-cors runtime <2.1.0,>=2.0.0 2.2.0 2.2.0 MIT sanic-cors runtime
==0.9.9.post1 2.2.0 2.2.0 MIT sanic-jwt runtime <2.0.0,>=1.6.0 1.8.0 1.8.0 MIT
sanic-jwt runtime ~=1.3 1.8.0 1.8.0 MIT sanic-prometheus runtime (~=0.2.1) 0.2.1
0.2.1 MIT sanic-routing runtime <0.8.0,>=0.7.2 23.12.0 23.12.0 MIT scikit-learn
python_versi... <1.2,>=0.22 1.5.2 1.5.2 Other scikit-learn python_full_...
<1.1,>=0.22 1.5.2 1.5.2 Other scikit-learn runtime ~=0.20.2 1.5.2 1.5.2 Other
scipy python_full_... <1.7.3,>=1.4.1 1.14.1 1.14.1 BSD-3-Clause scipy
python_versi... <1.11.0,>=1.... 1.14.1 1.14.1 BSD-3-Clause scipy runtime ~=1.2
1.14.1 1.14.1 BSD-3-Clause sentencepiece[sentencepiece] extra == "tr...
<0.2.0,>=0.1.99 sentry-sdk runtime <1.15.0,>=0.... 2.14.0 2.14.0 MIT setuptools
runtime >=65.5.1 75.1.0 75.1.0 MIT setuptools runtime >=41.0.0 75.1.0 75.1.0 MIT
sklearn-crfsuite runtime <0.4,>=0.3 0.5.0 0.5.0 MIT sklearn-crfsuite runtime
~=0.3.6 0.5.0 0.5.0 MIT slack-sdk runtime <4.0.0,>=3.19.2 3.33.1 3.33.1 MIT
slackclient runtime ~=1.3 2.9.4 2.9.4 MIT spacy (sys_platfor... <4.0,>=3.4 3.8.1
3.8.1 MIT spacy (sys_platfor... <3.5,>=3.1 3.8.1 3.8.1 MIT spacy runtime
<2.2,>=2.1 3.8.1 3.8.1 MIT spacy extra == 'sp... (<2.2,>=2.1) 3.8.1 3.8.1 MIT
structlog runtime <24.0.0,>=23... 24.4.0 24.4.0 Apache-2.0/MIT structlog-sentry
runtime <3.0.0,>=2.0.2 2.1.0 2.1.0 MIT tarsafe runtime <0.0.5,>=0.0.3 0.0.5
0.0.5 MIT tensor2tensor runtime ~=1.14.0 1.15.7 1.15.7 Apache-2.0 tensorflow
sys_platform... ==2.12.0 2.17.0 2.17.0 Apache-2.0 tensorflow-cpu runtime
~=1.15.0 2.17.0 2.17.0 Apache-2.0 tensorflow-cpu-aws sys_platform... ==2.12.0
2.15.1 2.15.1 Apache-2.0 tensorflow-hub runtime ~=0.6.0 0.16.1 0.16.1 Apache-2.0
tensorflow-hub runtime (~=0.10.0) 0.16.1 0.16.1 Apache-2.0 tensorflow-intel
sys_platform... ==2.12.0 2.16.2 2.17.0 Apache-2.0 tensorflow-io-gcs-filesystem
sys_platform... ==0.32 0.37.1 0.37.1 Apache-2.0 tensorflow-io-gcs-filesystem
sys_platform... ==0.32 0.37.1 0.37.1 Apache-2.0 tensorflow-io-gcs-filesystem
sys_platform... ==0.31 0.37.1 0.37.1 Apache-2.0 tensorflow-macos sys_platform...
==2.12.0 2.16.2 2.16.2 Apache-2.0 tensorflow-metal (sys_platfor... ==0.8.0 1.1.0
1.1.0 AML tensorflow-probability runtime ~=0.7.0 0.24.0 0.24.0 Apache-2.0
tensorflow-text sys_platform... ==2.12.0 2.17.0 2.17.0 Apache-2.0
tensorflow-text runtime ~=1.15.1 2.17.0 2.17.0 Apache-2.0 tensorflow-text extra
== 'co... (~=1.15.1) 2.17.0 2.17.0 Apache-2.0 tensorflow_hub runtime
<0.14.0,>=0.... 0.16.1 0.16.1 Apache-2.0 terminaltables runtime <3.2.0,>=3.1.0
3.1.10 3.1.10 MIT terminaltables runtime ~=3.1 3.1.10 3.1.10 MIT text2digits
runtime (==0.1.0) 0.1.0 0.1.0 MIT tqdm runtime <5.0,>=4.31 4.66.5 4.66.5
MPL-2.0/MIT tqdm runtime ~=4.0 4.66.5 4.66.5 MPL-2.0/MIT transformers extra ==
"tr... <=4.26.0,>=4... 4.44.2 4.44.2 Apache-2.0 twilio runtime <8.3,>=6.26 9.3.1
9.3.1 MIT twilio runtime ~=6.0 9.3.1 9.3.1 MIT typing-extensions runtime
<5.0.0,>=4.1.1 4.12.2 4.12.2 PSF-2.0 typing-utils runtime <0.2.0,>=0.1.0 0.1.0
0.1.0 Apache-2.0 ujson runtime <6.0,>=1.35 5.10.0 5.10.0 BSD-3-Clause
webexteamssdk runtime <1.7.0,>=1.1.1 1.6.1 1.7 MIT webexteamssdk runtime ~=1.1
1.6.1 1.7 MIT websockets runtime <11.0,>=10.0 13.0.1 13.0.1 BSD-3-Clause wheel
runtime >=0.38.1 0.44.0 0.44.0 MIT

PROJECT STATISTICS

Sourcerank 15 Repository Size 1.51 GB Stars 18,563 Forks 4,591 Watchers 352 Open
issues 124 Dependencies 286 Contributors 440 Tags 783 Created Oct 14, 2016 Last
updated 21 days ago Last pushed about a month ago

TOP CONTRIBUTORS SEE ALL



--------------------------------------------------------------------------------

PACKAGES REFERENCING THIS REPO

RASA

Open source machine learning framework to automate text- and voice-based
conversations: NLU, dial...
Latest release 3.6.20 - Updated Apr 18, 2024 - 18.6K stars

RASA-PRO

Rasa Pro package
Latest release 0.0.1.post1 - Updated Mar 20, 2024 - 18.6K stars

RASA-PLUS

Rasa Plus package
Latest release 0.4.0 - Updated Aug 24, 2022 - 18.6K stars

BOTSFACT

Open source machine learning framework to automate text- and voice-based
conversations: NLU, dial...
Latest release 1.8.1 - Published Mar 11, 2020 - 18.6K stars

PROJ-CDG

Open source machine learning framework to automate text- and voice-based
conversations: NLU, dial...
Latest release 1.8.1 - Published Mar 11, 2020 - 18.6K stars

RASAFOU

Open source machine learning framework to automate text- and voice-based
conversations: NLU, dial...
Latest release 1.7.49 - Updated Mar 3, 2020 - 18.6K stars

RASA-HYDRA

Forked from the open source machine learning framework, Rasa
Latest release 3.6.0 - Updated Feb 9, 2023 - 18.6K stars

BOTSFACTORY

Open source machine learning framework to automate text- and voice-based
conversations: NLU, dial...
Latest release 1.6.0 - Published Jan 13, 2020 - 18.6K stars

BOTSF

Open source machine learning framework to automate text- and voice-based
conversations: NLU, dial...
Latest release 1.6.0 - Published Jan 10, 2020 - 18.6K stars

KDRASA

dialogue manager for enterprise
Latest release 0.3.10 - Updated Jul 23, 2019 - 18.6K stars

RASA-X

Rasa X placeholder package
Latest release 0.0.2 - Updated May 21, 2019 - 18.6K stars

RASA-NLU

Rasa NLU a natural language parser for bots
Latest release 0.15.1 - Updated Feb 21, 2021 - 18.6K stars


--------------------------------------------------------------------------------

RECENT TAGS SEE ALL

3.6.20 April 18, 2024 3.6.19 March 04, 2024 3.6.18 February 23, 2024 3.6.17
February 13, 2024 3.6.16 January 19, 2024 3.5.17 December 05, 2023 3.6.15
December 01, 2023 3.7.0 November 22, 2023 3.7.0rc4 November 22, 2023 3.6.14
November 20, 2023 3.7.0rc3 November 17, 2023 3.7.0rc2 November 13, 2023
3.7.0a1.dev20231108 November 08, 2023 3.7.0a1.dev20231107 November 07, 2023
3.7.0a1.dev20231106 November 06, 2023



--------------------------------------------------------------------------------

INTERESTING FORKS SEE ALL

CLASSICVALUES/RASA

💬 Open source machine learning framework to automate text- and voice-based
conversations: NLU, ...
Python - Apache-2.0 - Last pushed Jan 11, 2024 - 3 stars

FGA-GCES/RASA

💬 Open source machine learning framework to automate text- and voice-based
conversations: NLU, di...
Python - Apache-2.0 - Last pushed Sep 29, 2020 - 3 stars

FIMLM/HORMYBOT

💬 Open source machine learning framework to automate text- and voice-based
conversations: NLU, ...
Python - Apache-2.0 - Last pushed Jan 26, 2024 - 1 stars

ATARORA/RASA

💬 Open source machine learning framework to automate text- and voice-based
conversations: NLU, ...
Python - Apache-2.0 - Last pushed Mar 13, 2023 - 1 stars

MBHAVYA/RASA

💬 Open source machine learning framework to automate text- and voice-based
conversations: NLU, ...
Python - Apache-2.0 - Last pushed Mar 3, 2023 - 1 stars



Something wrong with this page? Make a suggestion

Last synced: 2024-08-08 02:40:36 UTC

Login to resync this repository

Libraries.io helps you find new open source packages, modules and frameworks and
keep track of ones you depend upon.

     

--------------------------------------------------------------------------------



Copyright © 2024 Tidelift, Inc
Code is Open Source under AGPLv3 license
Data is available under CC-BY-SA 4.0 license

Explore
 * Platforms
 * Languages
 * Licenses

 * About
 * Team
 * Terms and Conditions
 * Privacy Policy
 * API