- New AVE record submission
- Update to existing AVE record
- Schema change (v1.0.0)
- New detection rule (YARA / Semgrep / pattern)
- Crosswalk addition or update
- Documentation improvement
- Other:
- Linked issue confirms the id and that this is a new class, not a variant
- Record validates against
schema/ave-record-1.1.0.schema.json - All 15 required fields are present and non-empty
-
behavioral_fingerprintis one clear sentence describing what the component DOES -
indicators_of_compromisehas at least one entry a defender can actually search for -
owasp_mcpis present with at least one entry -
aivssblock is complete — required sub-fields: cvss_base, aars, thm, mitigation_factor, aivss_score, spec_version -
aivss.aivss_scoreagrees withseverity(CRITICAL >= 9.0, HIGH 7.0–8.9, MEDIUM 4.0–6.9, LOW < 4.0) - Top-level
aivss_scorematchesaivss.aivss_scoreif both are present -
referenceshas at least one citable primary source -
researcheris set - AARF rationale for each non-zero factor is in the PR description
- Coordinated scanner PR in bawbel/scanner is linked (rule + positive and negative fixtures)
- Responsible disclosure followed if this involves a specific component or publisher
-
last_updatedis set to today in ISO 8601 format - Change is explained in the PR description
- If
aivss_scorechanges: AARF rationale for each changed factor is in the PR description
- Issue opened first with 30-day comment period completed (structural changes only)
-
schema/ave-record.schema.json(alias) updated to mirror the new canonical - New versioned schema file added (e.g.
schema/ave-record-1.2.0.schema.json) — prior versioned files stay frozen, never edited - CHANGELOG.md updated
- Migration path for existing records documented
- I have read CONTRIBUTING.md
-
ave_idvalues are immutable — no renumbering - Schema version string is
1.0.0 - No references to SPEC.md (removed), template.json (removed), or bawbel/bawbel-ave (wrong path)
- I agree my contribution is licensed under Apache 2.0