...

We have not had any notable releases of the combined Cactus codebase, although there are previous releases of the BIF and ConnectionChain.  We hope to have a full Cactus release in the not too distant future.

The releases will be pushed to npm and in a monorepo format but under the npm scope of @hyperledger meaning that the project name will not be the npm scope but rather just a prefix prior to the package name. This makes it much wordier for the package names, but the upside is that we are consistent with the global Hyperledger npm scope. So the package names will be like this for exmaple:

• @hyperledger/cactus-cmd-api-sever,
• @hpyerledger/cactus-common
• @hyperledger/cactus-sdk,
• etc.. 

It is not too late to change the package naming theme if the TSC would rather have us our own npm scope such as:

• @cactus/cmd-api-server
• @cactus/common
• @cactus/sdk

Which is easier to read (less verbose), but may be confusing to users who expect all legit Hyperledger projects to publish under the same @hyperledger npm scope.

Overall Activity in the Past Quarter

...