Maturity: Code Object

Maturity Spectrum Rationale

Semantic Consensus: Medium

There are a few existing semantic issues around the Code Object:

1. The Code_Purpose field is intended to capture the purpose behind a particular code snippet, something which could be quite arbitrary; it currently uses a limited enumeration (the CodePurposeEnum) to achieve this. Thus, the utility of this field is not clear, and it's unlikely to be useful or used consistently across implementations.
2. The Digital_Signatures field uses the DigitalSignaturesType from CybOX Common instead of the X509 Certificate Object.

Semantic Completeness: Medium

There exists the potential for additional fields around the Code Object, such as for capturing the cryptographic hash of the code.

Existing Use: Low

There is no documented use of the Code Object.