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

test: add fuzzer #3353

Closed
wants to merge 1 commit into from
Closed

test: add fuzzer #3353

wants to merge 1 commit into from

Conversation

LeoDog896
Copy link
Contributor

Description

Result

Adds an npm run fuzz command that can be used to fuzz the parse and parseInline functions and their suboptions.

Contributor

  • Test(s) exist to ensure functionality and minimize regression (if no tests added, list tests covering this PR); or,
  • no tests required for this PR.
  • If submitting new feature, it has been documented in the appropriate places.

Committer

In most cases, this should be a different person than the contributor.

Copy link

vercel bot commented Jun 27, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
marked-website ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 27, 2024 2:20am

@UziTech
Copy link
Member

UziTech commented Jun 27, 2024

looks like https://www.npmjs.com/package/@jazzer.js/core is no longer maintained

@LeoDog896
Copy link
Contributor Author

LeoDog896 commented Jun 27, 2024

looks like https://www.npmjs.com/package/@jazzer.js/core is no longer maintained

It seems so! It was also mentioned in oss-fuzz now that I see - google/oss-fuzz#11652

I assume this would be blocking for fuzzing integration, then.

@UziTech
Copy link
Member

UziTech commented Jun 27, 2024

I think that would be blocking. I don't want to introduce a dependency on something that could become a vulnerability.

The irony 🤣

@LeoDog896
Copy link
Contributor Author

Alright! If google/oss-fuzz#11652 gets resolved, I'll reopen all the relevant issues & PRs 👍

@LeoDog896 LeoDog896 closed this Jun 27, 2024
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.

2 participants