Skip to content

Remove the recently added nvd alias #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 4, 2022

Conversation

joshrotenberg
Copy link
Contributor

@joshrotenberg joshrotenberg commented Dec 21, 2021

See #31 for reasons and discussion.

This PR completely removes the alias and the documentation. EDIT: refactored to mark the :security/nvd alias as deprecated as there is potential for false positives from the clojure-nvd library being included on the classpath

@practicalli-johnny
Copy link
Contributor

Thanks. I am going to leave the security/nvd alias there for a couple of weeks, so people have time to look at it.
I added a description to explain the issue for now.
It's a very useful tool and would have been a great addition if it were not for the constraints.

Once I've added this tool to the book I'll merge the PR.

On advice from the clojure-nvd project maintainer, using clojure-nvd from an
alias is not recommended.  The clojure-nvd library itself would be included in
the security check and potentially create false positives

Mark the :security/nvd alias as deprecated and add warning to README
@practicalli-johnny
Copy link
Contributor

I am going to leave the :security/nvd alias as deprecated for the present time, rather than simply remove it. It will help highlight the potential for false positives in using clojure-nvd with a Clojure CLI alias.

I've updated the pull request accordingly (which also gave me chance to remember how to do that in Magit :) )

@practicalli-johnny practicalli-johnny merged commit bf98046 into practicalli:live Jan 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants