How to Access Execution Time & Crash Count Data for OSS-Fuzz Projects?

[Vinay152003]

Hi OSS-Fuzz Team,

I'm working on a project for GSoC 2025 titled "Streamlined Experiment Execution and Improved Report UI (OSS-Fuzz-Gen)". One of the key objectives is to enhance the reporting system by including detailed experiment execution insights.

Currently, I can fetch details like project name, language, repository, code coverage, and fuzzer count. However, I noticed that execution time and crash count data are missing from publicly available sources like:

OSS-Fuzz Introspector
Project-specific dashboards
Could you clarify:

Where can we access execution time and crash count data for OSS-Fuzz projects?
Does OSS-Fuzz provide an API or any public endpoint that includes this information?
Are there alternative sources like public bug trackers or periodic reports that list this data?
Additional Context (Access Issues)
I also tried checking oss-fuzz.com for this data, but I encountered an "Access Denied" message (screenshot attached).

Is this data restricted to project maintainers, or is there a way for external users to access it?
If access is required, what are the steps to request permission?
This information would be incredibly helpful for improving our reporting system. Looking forward to your guidance—thanks in advance! 😊

@DavidKorczynski @mikea @mikeal @alex @bgianfo @haberman @DonggeLiu

[DonggeLiu]

Hi Vinay, Thanks for reaching out. To clarify the main goal of the project: Project 8 (Self-Contained OSS-Fuzz Module) aims to enhance the robustness and accessibility of OSS-Fuzz functions for researchers using OSS-Fuzz-Gen. Hence it's better to focus on and prioritize the OSS-Fuzz features that already used by OSS-Fuzz-Gen. *Preparatory Steps* I recommend starting from the following aspects, as they will be expected in your project proposal: 1. Collecting a list of existing OSS-Fuzz features and data currently utilized by OSS-Fuzz-Gen (include and beyond those mentioned in our project description and oss_fuzz_checkout.py <https://github.com/google/oss-fuzz-gen/blob/main/experiment/oss_fuzz_checkout.py>). This can be a really good starting point to prepare for the project. 2. Proposing a list of additional features or data that could benefit OSS-Fuzz-Gen. 3. Writing a design plan for a self-contained module that provides these features and data to researchers (e.g., tailored to OSS-Fuzz-Gen use cases) without modifying the OSS-Fuzz source code directly. 4. Writing a timeline for implementation. *Relevant Repositories* OSS-Fuzz-Gen <https://github.com/google/oss-fuzz-gen> is the main repo, you might need to occasionally look up relevant feature/data details in OSS-Fuzz <https://github.com/google/oss-fuzz>. Some features/data also relates to fuzz-introspector <https://github.com/ossf/fuzz-introspector>, but that's not a high priority at this moment. Best regards, Dongge Liu, PhD (UniMelb)

…

On Wed, 19 Mar 2025 at 06:08, Vinay Hipparge ***@***.***> wrote: Hi OSS-Fuzz Team, I'm working on a project for GSoC 2025 titled "Streamlined Experiment Execution and Improved Report UI (OSS-Fuzz-Gen)". One of the key objectives is to enhance the reporting system by including detailed experiment execution insights. Currently, I can fetch details like project name, language, repository, code coverage, and fuzzer count. However, I noticed that execution time and crash count data are missing from publicly available sources like: OSS-Fuzz Introspector <https://introspector.oss-fuzz.com/> Project-specific dashboards Could you clarify: Where can we access execution time and crash count data for OSS-Fuzz projects? Does OSS-Fuzz provide an API or any public endpoint that includes this information? Are there alternative sources like public bug trackers or periodic reports that list this data? Additional Context (Access Issues) I also tried checking oss-fuzz.com for this data, but I encountered an "Access Denied" message (screenshot attached). Is this data restricted to project maintainers, or is there a way for external users to access it? If access is required, what are the steps to request permission? This information would be incredibly helpful for improving our reporting system. Looking forward to your guidance—thanks in advance! 😊 issue.png (view on web) <https://github.com/user-attachments/assets/98314756-9cc2-48b6-b8f3-9b0e4e5aa12f> @DavidKorczynski <https://github.com/DavidKorczynski> @mikea <https://github.com/mikea> @mikeal <https://github.com/mikeal> @alex <https://github.com/alex> @bgianfo <https://github.com/bgianfo> @haberman <https://github.com/haberman> @DonggeLiu <https://github.com/DonggeLiu> — Reply to this email directly, view it on GitHub <#13148>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE4NLSJBYHHKUHQRHVVUUQD2VBVLDAVCNFSM6AAAAABZI7J4XCVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZYGEYDAMBSGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Vinay152003]

Project 8: Self-Contained OSS-Fuzz Module – Project Planning Document

Author: Vinay Hipparge
GSoC 2025 Contributor Applicant

---

👋 Hi Dongge Liu,

I’ve completed the preparatory steps suggested by @DonggeLiu and compiled a detailed project planning document for Project 8: Self-Contained OSS-Fuzz Module.

📄 The attached PDF includes:

• ✅ A comprehensive list of existing OSS-Fuzz features and data currently used by OSS-Fuzz-Gen (extending beyond oss_fuzz_checkout.py)
• ✅ A proposed list of additional features that could further enhance OSS-Fuzz-Gen
• ✅ A modular design plan for accessing and extending OSS-Fuzz functionality without modifying OSS-Fuzz itself
• ✅ A full GSoC-aligned implementation timeline (June–November 2025), broken down by milestone

📎 Attachment: Vinay152003.pdf

---

🙏 Request for Feedback

I'd really appreciate your feedback on the following areas:

🔍 Additional OSS-Fuzz Data Sources

• Are there other valuable data sources within OSS-Fuzz (or related projects) that I should consider for integration?

🧩 Modular Design

• Does the proposed design abstraction and interface-based extension approach look robust for long-term maintainability and external usability?

🧪 Integration & Researcher Wishlist

• Any integration concerns, especially for researchers leveraging OSS-Fuzz-Gen?
• Are there features or insights researchers would love to extract that I haven’t addressed?

---

Looking forward to your thoughts and guidance!

Best regards,
Vinay Hipparge
GSoC 2025 Contributor Applicant

[DonggeLiu]

Hi @Vinay152003 thanks for the PDF.
The project is modularizing the OSS-Fuzz features used by OSS-Fuzz-Gen, hence is not suitable for this repo.
I will close this discussion and reply to your via email.