Add CME (Common Mitigation Enumeration) control namespace + publisher entity stub#97
Merged
Conversation
… entity stub
Wire the CME prototype taxonomy (github.com/stuwrtlttle/cme) into the registry
as a control namespace, mirroring the MITRE publisher pattern (entity + type
file under one DNS-authority namespace).
- control/com/github/stuwrtlttle.{json,md}: name-level node `cme`, children
match `^CME-\d{3,4}$` (anchored, bounded quantifier — no catastrophic
backtracking). Two resolution URLs per item: raw JSON (weight 100,
parsability structured) and GitHub rendered view (weight 50, scraped).
- entity/com/github/stuwrtlttle.json: publisher stub so the control's
`operator:` pointer resolves; `cme` node cross-references via
issues_type/issues_namespace.
- Registry scope is identity + resolution only; per-control data (CVSS
attenuation, CWE relationships) is deferred to a future Data layer.
- Refresh namespace counts (2030).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Wires the CME (Common Mitigation Enumeration) prototype taxonomy into the registry as a
controlnamespace, plus a publisherentitystub.CME enumerates defensive controls (the mitigation counterpart to CVE/CWE), each mapped to a deterministic CVSS environmental attenuation and to CWE weakness classes. Hosted at github.com/stuwrtlttle/cme.
Structure (mirrors the MITRE publisher pattern)
github.com/stuwrtlttleregistry/entity/com/github/stuwrtlttle.jsonsecid:entity/github.com/stuwrtlttleregistry/control/com/github/stuwrtlttle.{json,md}secid:control/github.com/stuwrtlttle/cmesecid:control/github.com/stuwrtlttle/cme#CME-601The
cmename lives inmatch_nodes;CME-NNNIDs are subpaths (children) — same shape asmitre.org/cve#CVE-....Resolution (two URLs per item)
parsability: structured,content_type: application/json(AI-first primary)parsability: scraped(human-readable)Notes
^CME-\d{3,4}$is fully anchored with a bounded quantifier — no catastrophic backtracking.schemaSecID omitted (schema file listed as a plain URL instead); entity is a stub.schemas/registry-namespace.schema.json.Deploy
Merging touches
registry/**/*.json→ triggers the auto-deploy chain to the live resolver.