. A ZIP file is a Windows binary, and therefore it will not be too interesting. What you want to see is the contents of the .tar.gz archive. You can extract this content, and then look at the code in the R subdirectory.
You can also upgrade the package to work with new versions of R so that you can actually create and install the package. To do this, you can unzip the .tar.gz file as before, but now you need to add the NAMESPACE file. This is just a plaintext file at the top of the package directory, which has a form like:
export(createar) export(createwgn) export(criticalvaluesWCO) export(criticalvaluesWSP) export(cwt.ts) export(plot.wt) export(plotwt) export(readmatrix) export(readts) export(rk) export(wco) export(wcs) export(writematrix) export(wsp)
If you have an export statement for any package function that you really want to use. If the function is not exported, then the functions in the package still have access to this function, but the user cannot use it (as easy). After that, you can create and install the package.
I took the liberty of making any of this already. I actually did not find the time to figure out which functions are useful and should be exported, and simply assumed that if a help page was written for the function that it should export, and if there was no help page, then export it. I used Rd2roxygen to convert the help pages to roxygen code (because it's like I roll), and after that you had to clean up the cleanup a bit, but it seems to be just fine.
So, if you have the devtools package installed, you can really install the version that I modified directly using the following commands
library(devtools) install_github("SOWAS", "Dasonk")
Personally, I would recommend that you go along the path of adding the NAMESPACE file, and not directly, because then you will have more control over the code and you can fix any problems that may occur when using the package. Or, if you use git, you can unlock my repo and continue to fix things from there. Good luck.