https://bitbucket.org/cse-assemblyline/assemblyline/commits/...
Couple interesting bits:
1. Bcrypt looks trusted. I guessed as much given that I've seen it used in other GC projects that were "Protected B" (think Revenue Canada / similar).
2. It doesn't look like they enabled HSTS by default until a couple months later in the repo:
https://bitbucket.org/cse-assemblyline/assemblyline/commits/...
Again, unsurprising since the CSE / CST main page doesn't have HSTS.
3. This part of the original version of the README is interesting:
#### License (or lack thereof) and Conditions of use
As is fairly evident, we haven't selected a license for this project as of yet. As discussed when members were first granted read access to the repository, dissemination is based on the premise of originator controlled. If you feel there are other partners that would benefit from an early view and would be able to contribute, please contact the project leads and we should be able to sort it out.
We will soon be splitting the platform and services into two separate repo's, so please treat the services as slightly more sensitive than the platform itself, ie: release it and perish!!! ... but seriously, we do not grant anyone the right to do anything other than deploy the platform and use it. No sharing, presenting, etc without our knowledge.
We hope to have a clear release plan soon.
So it looks like they passed it around a bit either internally in the CSE or to a wider audience that may have included other departments. Probably getting more eyes on it to stop something stupid from going out.
4. There are some fun little commits like this:
https://bitbucket.org/cse-assemblyline/assemblyline/commits/...
Or this (adding the French version is always one of the last steps before something goes public):
https://bitbucket.org/cse-assemblyline/assemblyline/commits/...
Or this (we've all been there):
https://bitbucket.org/cse-assemblyline/assemblyline/commits/...