Flag security alerts and pass versions through

[mwaddell]

closes #84
closes #102

[mwaddell]

I still need to add test coverage to the new getAlert method which uses graphQL and update the documentation, but it's pretty close...

[mwaddell]

Updated documentation and addressed unit tests

[brrygrdn]

This is awesome, thank you ❤️

I have one thought that might be a bit defensive. This is adds a call to the GitHub API that might be wasted if users don't care about these values - should we use an input flag, which defaults to false to ensure the query is only invoked when explicitly requested? 🤔

I love this pattern of using the API to enrich the metadata further, but it might be worth setting a precedent of doing the least work by default.

[mwaddell]

I have one thought that might be a bit defensive. This is adds a call to the GitHub API that might be wasted if users don't care about these values - should we use an input flag, which defaults to false to ensure the query is only invoked when explicitly requested? thinking

I love this pattern of using the API to enrich the metadata further, but it might be worth setting a precedent of doing the least work by default.

Yes, that makes perfect sense - I'll add that and assign it back for review

[mwaddell]

Done

[brrygrdn]

Thanks for this @mwaddell! I just want to do a minor release to get some house keeping updates out of the way and I'll get this merged 🚀