Add OWASP Juice Shop metadata

[owasp-nest]

⚠️ This PR has been generated by Arkadii Yakovets as part of the OWASP Schema initiative within OWASP Nest.

OWASP Entity Information

• Project: OWASP Juice Shop
• Repository: OWASP/www-project-juice-shop
• Metadata generated on: 2025-10-05

Changes

This PR adds the project data to comply with the OWASP Schema specification. The changes include:

• The metadata file in YAML format
• Schema validation GitHub Actions workflow

Purpose

This addition ensures that the project data follows the standardized OWASP Schema format, enabling:

• Better data consistency across OWASP entities
• Improved automation and tooling capabilities
• Enhanced data validation and quality
• Streamlined integration with OWASP Nest platform

Review Guidelines

When reviewing this PR, please focus on:

1. Data Accuracy: Verify that the entity information is correct (type, level, leaders, tags, URLs)
2. Schema Compliance: Ensure all required fields are present and properly formatted
3. YAML Syntax: Check for proper YAML formatting and indentation
4. Content Quality: Review the completeness and accuracy of the data

Support & Questions

If you have any questions about this PR or the OWASP Schema implementation:

• PR Author Slack: Arkadii Yakovets
• PR Author GitHub: @arkid15r
• OWASP Nest Slack Channel: #project-nest
• Documentation: OWASP Schema documentation

---

Closes OWASP/nest-schema#140

[bkimminich]

Missing a ton of relevant links, e.g. social media, Download options, DockerHub image, Merchandise, etc.etc.

[bkimminich]

I would not want to have to maintain this schema file alongside our existing info.md redundantly. Either everything needs to be supported in the schema and the website sidebar is generated from it, or it needs to generate at least the supported parts and the info.md is then just appended underneath for additional custom links not supported in the schema.

[bkimminich]

Please see previous two comments.

[bkimminich]

@arkid15r, please take a look at my comments and provide feedback. I'm not merging something so clearly AI generated and not humanly curated. The maintenance follow-up work is unclear and I'm not sure if there will be loss of information or duplication of content on some scale.

cc/ @mamicidal

[arkid15r]

@bkimminich I'm assuming positive intent, but I'd like to ask to refrain from commenting on areas they don't fully understand, including the scope of work already completed or still WIP. Nobody likes duplicated effort but here I am answering your questions both here and on Slack because I have a goal and want to see it completed.

Here are some links to work that has clearly been AI-generated and not humanly curated:

• https://github.com/OWASP/Nest/issues?q=is%3Aissue%20state%3Aclosed%20milestone%3A%22OWASP%20Schema%22
• https://github.com/OWASP/nest-schema/pulls?q=is%3Apr+is%3Aclosed
• https://github.com/OWASP/nest-schema/issues

I'm not going to push anyone into doing something they don't want to as project leaders.

[bkimminich]

Hi @arkid15r! I have updated the YAML in this PR to contain every information that Juice Shop needs. This fails the schema validation of course, as some fields or enum values are missing:

• license enum missing CC-BY-NC-ND-4.0
• social_media enum missing facebook as platform
• community enum missing matrix and reddit as platforms

I will merge the PR now anyhow and propose a change to the NEST schema afterwards.

[arkid15r]

@bkimminich thanks for merging this 👍