https://github.com/webreflection/csp
Because Security Matters, and Web libraries, tools, and projects, should be more informative about their state.
https://github.com/webreflection/csp
badge csp security
Last synced: 4 months ago
JSON representation
Because Security Matters, and Web libraries, tools, and projects, should be more informative about their state.
- Host: GitHub
- URL: https://github.com/webreflection/csp
- Owner: WebReflection
- Created: 2021-02-19T14:31:57.000Z (over 5 years ago)
- Default Branch: main
- Last Pushed: 2021-12-30T09:59:38.000Z (over 4 years ago)
- Last Synced: 2025-01-16T09:43:14.218Z (over 1 year ago)
- Topics: badge, csp, security
- Homepage:
- Size: 157 KB
- Stars: 15
- Watchers: 3
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Security: security-matters.jpg
Awesome Lists containing this project
README
# CSP Badge   

**Social Media Photo by [Franck](https://unsplash.com/@franckinjapan) on [Unsplash](https://unsplash.com/)**
---
This repository exists only to allow other repositories to add a *badge* about the [CSP](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) state of the module, library, or helper.
The offered *SVG* images are the following:
*  suitable for projects that *don't* use `eval` or `Function` or scripts served as `Blob`, hence don't ever need any particular *CSP* rule
*  suitable for projects that *might need* particular *CSP* rules to fully work as expected
*  for all projects humble enough to declare such project is *everything but secure*, and inform users about the risk they might have if such project is used in production
---
##  CSP strict
The project does *not* need any specific [CSP](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) configuration because it does *not* include, use, or inject, any *Function*, *eval*, or other workarounds to evaluate anything at all, hence the security is granted to be the best possible.
---
##  CSP friendly
The project *might* need some specific [CSP](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) configuration, because it could need to use *Function*, *eval*, or any other workaround to evaluate code at runtime, hence security needs to be considered, and best practices followed.
---
##  CSP hostile
The project shamelessly needs, use, or pollute the running software, with *Function*, *eval*, or any other workaround to evaluate code at runtime, so that even [CSP](https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP) might not be enough to grant a secure execution of the program.
---
### How to include
If your project would like to inform its users about its *CSP* compliancy, you can add one of these badges on top of your *GitHub*, *GitLab*, or any other service, so that it'll be instantly visible:
**Markdown** - Basic
```md



```
**Markdown** - Informative
```md
[](https://webreflection.github.io/csp/#-csp-strict)
[](https://webreflection.github.io/csp/#-csp-friendly)
[](https://webreflection.github.io/csp/#-csp-hostile)
```
**HTML** - Basic
```html
```