AFLplusplus/LibAFL

libafl_libfuzzer needs a better publication strategy

Open

#1,534 opened on Sep 20, 2023

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Rust (476 forks)github user discovery
help wantedlibafl_libfuzzer

Repository metrics

Stars
 (2,615 stars)
PR merge metrics
 (Avg merge 17d 22h) (10 merged PRs in 30d)

Description

With the merge of #1525, we reintroduced path deps for libafl. We need to figure out a way to publish this crate more effectively, because we cannot use path deps in the embedded crate on publish, but we also must use path deps for ensuring that our tests are relevant on the main branch.

Contributor guide

Research direction
Investigate the merge of PR #1525 to understand the reintroduction of path dependencies, and research common strategies for publishing crates with path dependencies (e.g., using workspace dependencies, conditional path deps with features, or release automation scripts). Propose a solution to allow tests to use path deps while publishing with crates.io compatible dependencies.
Tech stack
rust
Domain
build system
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
RustCargo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30