-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add dateRejected to Published.cveMetadata #88
Comments
Agree. Few other date fields from PUBLISHED subschema make sense in REJECTED subschema such as dateAssigned, datePublished, datePublic. The timeline object may also make sense. |
Should this be closed given that https://github.com/CVEProject/cve-schema/pull/91/files is merged? Thanks! |
rc3 takes care of this. |
rsc
added a commit
to rsc/cve-schema
that referenced
this issue
Sep 14, 2021
Follow-up work for CVEProject#87 and CVEProject#88: an introduction to the new product and version schemas. Posted for easier reading at https://gist.github.com/rsc/0b448f99e73bf745eeca1319d882efb2.
rsc
added a commit
to rsc/cve-schema
that referenced
this issue
Sep 16, 2021
Follow-up work for CVEProject#87 and CVEProject#88: an introduction to the new product and version schemas. Posted for easier reading at https://gist.github.com/rsc/0b448f99e73bf745eeca1319d882efb2.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the Published.cveMetadata object, when “state” is “PUBLISHED”, “datePublished” can be used to find the date when the CVE was published. But when “state” is “REJECTED”, there is no corresponding date.
We propose to add “dateRejected” to fill this gap.
The text was updated successfully, but these errors were encountered: