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.

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

[ossf-scorecard] Add first fuzzer #7269

Merged
merged 1 commit into from
Feb 12, 2022

Conversation

AdamKorcz
Copy link
Collaborator

Adds the first fuzzer for ossf-scorecard to get the fuzzing started.

@justaugustus @naveensrinivasan

@DavidKorczynski DavidKorczynski merged commit ae1d148 into google:master Feb 12, 2022

package policy

func FuzzParseFromYAML(data []byte) int {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I would rather have the fuzzing code within the scorecard. Is there a specific reason to keep idt outside?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we change the API now someone in oss-fuzz would have to maintain this, with go 1.18 support fuzzing would be have been much easier compared to go-fuzz

Copy link
Collaborator Author

@AdamKorcz AdamKorcz Feb 12, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No problem. I will make a PR upstream with a Go 1.18 fuzzer shortly.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds good. Thanks! Then we can remove this from here.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Go 1.18 fuzzer added here: ossf/scorecard#1631

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants