Multiples wiki issues.

Typos

• https://github.com/infobyte/faraday/wiki/Executive-Report#using-markdown-on-a-report: -lenguage +language

Bad links

• https://github.com/infobyte/faraday/wiki/Executive-Report#requirements: https://github.com/infobyte/faraday/wiki/first-steps, the nedpoint first-steps doesn't exist anymore.

Images

• https://github.com/infob

(This old idea popped up to my mind while discussing #219.)

To be both consistent and more intuitive, etc/plugins.txt should be rename etc/plugins.ini.

*.ini or *.conf carry a meaning, whereas *.txt is not. Since the base of cve-search uses *.ini , let's stick to that. Python configparser documentation also refer to "INI fi

The database is saved to and used from the current directory versus somewhere better like ~/.vfeed/. This hampers several things, but most notably putting a symlink somewhere in my path to be able to call/use vfeedcli.py from any directory (cd ~/bin; ln -s path/to/vFeed/vfeedcli.py vfeed) like a system-wide command.

Btw, I have a patch for this already and will sent a PR shortly.

The table on the main README is pretty outdated.
It'd be great if someone could update it.

Adding a few entries from the repo to the table is already a valuable help 😈

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
We have date of disclosure on the backend, we need to expose it somewhere on the site and in the data.

Create an interface within the plugin to add notes, tags and other manually captured items analysts might want to keep track of, and have the notes displayed in the popups as well.

Any feedback or ideas for this are welcome.

Is your feature request related to a problem? Please describe.

Currently all the settings are rigidly defined at the project level (foo := defaultFoo in projectSettings). This means that the users can only override each of them at the project level - so Global/foo and ThisBuild/foo are ignored. This is inconvenient for multi-project builds, where it makes sense to provide project-wi

It would be helpful to have a more verbose output in the csv file format, the information would be the same as the html output has. The idea behind this request is the csv file is easier to consume by another application/script than html file.

This bug is reserved for new contributors only. If you already have a commit merged in cve-bin-tool, please leave this for people who don't!

In #387 I added a test_checkers.py file that contains a parametrized test for feeding filenames to the checkers to test the recognition, but only provided a couple of tests for python and one for bluez. You can [read about how to add this type of tes