Broad/Descriptive Tags On Entries about data HOT 6 CLOSED

That's an interesting question, the answer, at least for me is: "I don't know".

Right now the only two ""sponsors"" for this project are the Arachni and w3af projects, which are web scanners, thus all the vulnerabilities in this database would have the "website" or "http" tags (at least implicit). In the future this might change and someone (not me, and most likely not @Zapotek but I can't talk for him) might add vulnerabilities which are not web related.

It might be a good idea to prevent this future add-on of other vulnerabilities and tag all current vulnerabilities as "web", just in case.

Leaving open so we do that.

from data.

@andresriancho Which brings up the question, is vulndb just for web vulns or everything is fair game?

from data.

• The schema allows almost any type of vulns to be added.
• I'm not going to add any non-web vulns
• I'm not going to "block" any PRs for non-web vulns

Hope that clarifies my point of view

from data.

Thank god for unittests. As you say it wasn't valid JSON, that made the test fail and after a couple of quick fixes: https://circleci.com/gh/vulndb/data/33

from data.

@andresriancho It will be better if we merge develop to master with PR in the future. What do you think?

from data.

Yeah, I should work on develop and then merge. The good thing is that I'm only breaking master for some seconds ;)

from data.