**Changes:**

1. Renamed `cwe` to `category` to match the blueprint property.
2. Moved it under `properties` instead of a top-level mapping key.
3. Added standard mappings (`identifier`, `title`, `blueprint`) and a `selector` for completeness.

This ensures the `category` property is populated from `.attributes.classes[0].id`, so the aggregations filter correctly and the scorecard works.

Author: kodjomiles

docs/guides/all/owasp-top-10-scorecard.md

@@ -69,12 +69,18 @@ If the property is not yet included in your `Snyk Vulnerability` blueprint, foll
           ```yaml showLineNumbers
           resources:
             - kind: vulnerability
+              selector:
+                query: 'true'
               port:
                 entity:
                   mappings:
-                  //highlight-start
-                    cwe: .attributes.classes[0].id  
-                  //highlight-end
+                    identifier: .id
+                    title: .attributes.title
+                    blueprint: '"snykVulnerability"'
+                    properties:
+                      # highlight-start
+                      category: .attributes.classes[0].id
+                      # highlight-end
           ```
     </details>