add badge

[noraj]

Your tool/software have been inventoried on Rawsec's CyberSecurity Inventory.

What is Rawsec's CyberSecurity Inventory?

An inventory of tools and resources about CyberSecurity. This inventory aims to help people to find everything related to CyberSecurity.

• Open source: Every information is available and up to date. If an information is missing or deprecated, you are invited to (help us).
• Practical: Content is categorized and table formatted, allowing to search, browse, sort and filter.
• Fast: Using static and client side technologies resulting in fast browsing.
• Rich tables: search, sort, browse, filter, clear
• Fancy informational popups
• Badges / Shields
• Static API
• Twitter bot

More details about features here.

Note: the inventory is a FLOSS (Free, Libre and Open-Source Software) project.

Why?

• Specialized websites: Some websites are referencing tools but additional information is not available or browsable. Make additional searches take time.
• Curated lists: Curated lists are not very exhaustive, up to date or browsable and are very topic related.
• Search engines: Search engines sometimes does find nothing, some tools or resources are too unknown or non-referenced. These is where crowdsourcing is better than robots.

Why should you care about being inventoried?

Mainly because this is giving visibility to your tool, more and more people are using the Rawsec's CyberSecurity Inventory, this helps them find what they need.

Why the badge?

The badge shows to your community that your are inventoried. This also shows you care about your project and want it growing, that your tool is not an abandonware.

Also we took time to inventory your tool and you are gaining visibility from that: we added your tool to our inventory to make it known now it is your turn to add the badge to your project README to help our project being known.

Ok but...

You should think I asked nothing to you, I don't need visibility or/and I don't like your badge: your are free not to use it.

[coveralls]

Coverage remained the same at 92.206% when pulling 42b6462421735670ac9177667c2eb1e0862a04e7 on noraj:patch-1 into 22b671e15f0c8acdaed8594d0a8ae9f7c3303452 on arthepsy:master.

[coveralls]

Coverage remained the same at 92.206% when pulling 42b6462421735670ac9177667c2eb1e0862a04e7 on noraj:patch-1 into 22b671e15f0c8acdaed8594d0a8ae9f7c3303452 on arthepsy:master.

[coveralls]

Coverage remained the same at 92.206% when pulling 42b6462421735670ac9177667c2eb1e0862a04e7 on noraj:patch-1 into 22b671e15f0c8acdaed8594d0a8ae9f7c3303452 on arthepsy:master.

[coveralls]

Coverage remained the same at 92.206% when pulling 42b6462421735670ac9177667c2eb1e0862a04e7 on noraj:patch-1 into 22b671e15f0c8acdaed8594d0a8ae9f7c3303452 on arthepsy:master.

[rubo77]

@coveralls This repo is apparently no longer maintained (see

42).

@jtesta resumed development on a separate fork here, with many improvements: https://github.com/jtesta/ssh-audit