-
Notifications
You must be signed in to change notification settings - Fork 36
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
Statistic data about header usages. #61
Comments
Hi @riramar , I leveraged the resources provided by the free tier of GH for actions workflows with mermaid support to create set of little scripts to provide such statistics and update them every month automatically as well as the DB: https://github.com/righettod/oshp-stats I achieved gathering security headers infos for the first 200.000 entries of the Majestic Top 1 million site. I implemented an initial collection of the global statistics. All is documented on the project README and the repository is totally standalone. |
That's look amazing! How about make this available under our organization (https://github.com/oshp/) and include some references under https://owasp.org/www-project-secure-headers/ before closing this task? |
@riramar Indeed, it was the idea, can you create a new repo under the OSHP organization and grant me admin access on this new repo? I will transfer the content and continue to work on the project 😃 Thank you very much in advance 👍 |
Done via PR #65 |
Perfect! Thanks! |
I have tested the both workflows to update the DB and the stats MD file and there are both functional 👍 |
Description
Perform public to scan websites and view stats regarding these headers. Automated scanning of the top 1m sites on the web; filtering of said sites to view stats across industries and countries; published database dumps for public consumption/tools; scanning of individual sites; comparing multiple scanned sites.
Consistent reports regarding this secure headers, their usage, any changes to existing headers.
Additional resources
The text was updated successfully, but these errors were encountered: