Add OWASP CSRFGuard 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 CSRFGuard
• Repository: OWASP/www-project-csrfguard
• Metadata generated on: 2025-10-03

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#80

To fix this issue, you should add a permissions block to the workflow that explicitly sets the permissions granted to the GITHUB_TOKEN. Since neither the checkout nor the validation step are expected to require write access, the minimal privilege required is likely contents: read. You may add this block either at the top level (applies to all jobs) or under the validate-metadata job specifically. The best approach is to add it as a top-level key just below the workflow name, which will make the permission restriction explicit and protect against permission creep in future jobs. No new methods or imports are required—just a change to the YAML configuration file at the top level.