OSS-Fuzz initial integration: please confirm maintainer contact and approve PR
Hi @lukastaegert,
I've prepared an initial OSS-Fuzz integration for Rollup so it can be continuously fuzzed for free as part of Google's OSS-Fuzz program (https://github.com/google/oss-fuzz). Crashes/vulnerabilities are reported privately to the listed maintainers with a 90-day responsible-disclosure window.
OSS-Fuzz PR: https://github.com/google/oss-fuzz/pull/15510
The initial integration covers three fuzz targets against Rollup's public JavaScript API:
parseAst(the native Rust-based parser exposed viarollup/parseAst)getLogFilter(log-filter parsing exposed viarollup/getLogFilter)rollup()+bundle.generate()(full bundling pipeline using a virtual-module plugin)
Before this can be merged on the OSS-Fuzz side, the upstream maintainers need to:
Confirm the primary contact. I've listed
[email protected]inproject.yamlbased on recent commit activity, as that address will receive crash reports under the 90-day embargo. Please confirm this is the right address, or suggest an alternative (additional CCs are also welcome).Leave a comment / LGTM on the OSS-Fuzz PR acknowledging that the Rollup project agrees to the integration. The OSS-Fuzz reviewers require explicit upstream sign-off before merging a new project.
Happy to adjust the fuzz targets, contact list, or anything else you'd like changed. Thanks!
Source: rollup/rollup