Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,332
    • Merge requests 1,332
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #220062
Closed
Open
Issue created Jun 02, 2020 by Seth Berger@sethgitlabDeveloper

Establish gl-coverage-fuzzing-report.json schema

Problem to solve

Coverage guided fuzzing will emit a report with crashes and crash data. This data will be stored in gl-coverage-fuzzing-report.json as an artifact for users to review.

The schema of this report should be flexible to accommodate the data from various fuzzing engines.

This issue is to discuss the schema and what the json for gl-coverage-fuzzing-report.json will look like.

Please note that security report schemas are maintained in this project: https://gitlab.com/gitlab-org/secure/security-reports/

We should determine if we can use some of the existing schemas for the gl-fuzzing-report.json document.

Links / references

Edited Aug 05, 2020 by Seth Berger
Assignee
Assign to
Time tracking