Below you can find the official SensSoft release distrbution artifacts. Older releases can be found at the Apache SensSoft Archives. For ongoing development and future release announcements, stay tuned and sign up for our mailing lists to keep up to date!

Please Note all SensSoft artifacts are released as source code and binary artifacts and additional packages can be found on packaging platforms such as UserALE .js which we make available through the NPM useralejs package. The CHANGELOG file shipped with each artifact can be consulted for more information on the list of updates in each release. SensSoft artifacts are always distributed under the Apache License, version 2.0.

SensSoft UserALE.js

Please note, that for convenience, we make UserALE .js available through the NPM useralejs package.


The link in the 'Download Artifact' column below should display a default mirror selection based on your inferred location. If (when you browse to it) you do not see that page, try a different browser. The SHA512 checksum and ASCII armoured detached signatures are links to the originals on the main distribution server.
Version Download Artifact ASCII signature SHA512 Checksum
Apache SensSoft UserALE.js 1.0.0 (binary tar.gz) apache-senssoft-useralejs-1.0.0-bin.tar.gz apache-senssoft-useralejs-1.0.0-bin.tar.gz.asc apache-senssoft-useralejs-1.0.0-bin.tar.gz.sha512
Apache SensSoft UserALE.js 1.0.0(binary zip)
Apache SensSoft UserALE.js 1.0.0 (source tar.gz) apache-senssoft-useralejs-1.0.0-src.tar.gz apache-senssoft-useralejs-1.0.0-src.tar.gz.asc apache-senssoft-useralejs-1.0.0-src.tar.gz.sha512
Apache SensSoft UserALE.js 1.0.0(source zip)

Verify Releases

It is essential that you verify the integrity of the downloaded files using the PGP, and/or SHA signatures. published with every Gora release. Please read Verifying Apache HTTP Server Releases for more information on why you should verify our releases. We strongly recommend you verify your downloads with at least PGP. Guidance for doing so is provided below.

PGP Signatures

The PGP signatures can be verified using PGP or GPG. First download the KEYS as well as the asc signature file for the relevant distribution. N.B. Make sure you get these files from the main distribution directory, rather than from a mirror. Then verify the signatures using the following example

$ gpg --import KEYS

$ gpg --verify

The files in the most recent release are signed by Lewis John McGibbney (CODE SIGNING KEY) 48BAEBF6

SHA512 Signatures

Alternatively, you can verify the SHA512 signatures on the files. A unix program called md5 or md5sum is included in many unix distributions. Use the following example

$ sha512sum

... output should match the string in