So someone builds a nice secure and useful framework/platform which is great. But why not put some effort to mention some more details or documentation about how to use it, sample, tutorials etc?
For a specific example, see Section 8 of the paper (Building a Mylar Application) which starts with "To demonstrate how a developer can build a Mylar application, we show the changes that we made to the kChat application to encrypt messages."
Other than having a GUI and nice web interface, what are the advantages of Github over the git repo Mylar is using?
I don't expect other people in the research group to catch all of those types of errors, so a more openly collaborative environment would be an improvement. (I doubt R&R would set up an account for the UMass grad student who caught their error. The attempted replication that took him a month would have been much simpler if he could have git-cloned.) It doesn't have to be Github: Bitbucket would be fine. Even an academics-only or field-focused equivalent would get most of the way there, although it would exclude most interaction with the interested amateur public. Especially for those whose field is computer science, "maintaining" a Github account doesn't seem onerous.