Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Enforcing schema requirements #1

Merged
merged 1 commit into from
Jan 18, 2022
Merged

Enforcing schema requirements #1

merged 1 commit into from
Jan 18, 2022

Conversation

luigigubello
Copy link
Contributor

Enforcing security-insights-schema-1.0.0.yaml:

  • if threat-model-created is true, then evidence-url is required
  • if accepts-vulnerability-reports is true, then email-contact and security-policy are required

@luigigubello luigigubello merged commit 29447a5 into master Jan 18, 2022
@eddie-knight eddie-knight deleted the enforcing-schema-requirements branch September 29, 2023 16:16
eddie-knight pushed a commit that referenced this pull request Apr 12, 2024
@luigigubello
Merge pull request #1 from luigigubello/include-markdown
959978c 
Added a shortcode for importing the specification docs from the top level
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@luigigubello