遵循以下最佳实践的项目将能够自愿的自我认证,并显示他们已经实现了核心基础设施计划(OpenSSF)徽章。 显示详细资料
[](https://www.bestpractices.dev/projects/223)
<a href="https://www.bestpractices.dev/projects/223"><img src="https://www.bestpractices.dev/projects/223/badge"></a>
OWASP Juice Shop is probably the most modern and sophisticated insecure web application! It can be used in security trainings, awareness demos, CTFs and as a guinea pig for security tools! Juice Shop encompasses vulnerabilities from the entire OWASP Top Ten along with many other security flaws found in real-world applications!
The "bus factor" of OWASP Juice Shop is calculated as 1 by the truck-factor tool*. The constant maintainability "A"-grade and test coverage "A"-grade of CodeClimate (https://codeclimate.com/github/bkimminich/juice-shop) as well as the extensive documentation (https://pwning.owasp-juice.shop/part3/codebase.html) would allow others to pick up the project. OWASP as an organization also has experience in helping new Project Leaders to successfully take over an existing project.
(*last checked on 04.04.2018)
The project has 6+ unassociated significant contributors with >50 commits logged on GitHub: https://github.com/bkimminich/juice-shop/graphs/contributors
Copyright/License headers were added to source files with commit 99178d569925c0134c2951cda35b24b611617253 for OWASP Juice Shop v10.0.0.
Repository on GitHub, which uses git. git is distributed.
Beginner-friendly tasks are distinctly labeled on GitHub: https://github.com/bkimminich/juice-shop/labels/good%20first%20issue
The project leader and repository owner has 2FA enabled on his GitHub account.
GitHub offers 2FA via safe mechanisms (https://help.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/) and some of these are used by the project leader and repository owner.
Coding standards including the PR process are documented: https://pwning.owasp-juice.shop/part3/contribution.html. Failing to comply with the standard code style even automatically fails the build pipeline.
Reviews of PRs are spread across the 3 core project team members (https://github.com/bkimminich/juice-shop#contributors)
JavaScript project
All test suites are executable via documented npm scripts: https://pwning.owasp-juice.shop/part3/contribution.html#testing
npm
CI/CD Pipeline: https://github.com/juice-shop/juice-shop/actions/workflows/ci.yml
Test coverage is automatically gathered in LCOV format from unit and integration tests, accumulated during CI and sent to CodeClimate (https://codeclimate.com/github/bkimminich/juice-shop). The line coverage is typically between 85 and 90%.
Branch coverage is not monitored on CodeClimate but can be verified locally from LCOV output of the unit and integration tests.
Project website (https://owasp-juice.shop) and repository (https://github.com/bkimminich/juice-shop) as well as main download site (https://github.com/bkimminich/juice-shop/releases) are all hosted by GitHub. Additional download site SourceForge (https://sourceforge.net/projects/juice-shop/) also meets these requirements.
Users are encouraged to report unintentional vulnerabilities in order to have the project team either fix or incorporate them into the list of hacking challenges: https://github.com/bkimminich/juice-shop/security/policy
OWASP Juice Shop pins several outdated dependencues to make sure it keeps their known vulnerabilities to be able to provide corresponding hacking challenges.
The nature of OWASP Juice Shop as a vulnerable web application makes it an ideal target for DAST tools. Findings which are part of a hacking challenge will obviously not be fixed. The project used a weekly OWASP ZAP Baseline Scan (https://github.com/juice-shop/juice-shop/actions/workflows/zap_scan.yml) to find unintended vulnerabilities.
Due to its nature the Juice Shop only contains solution checks for all of its intentional hacking challenges.
后退