EFForg/rayhunter

Question on Dependency Security / Supply Chain Security

Open

#195 opened on Mar 25, 2025

View on GitHubContributor guide
 (9 comments) (1 reaction) (0 assignees)Rust (466 forks)github user discovery
documentationenhancementhelp wantedquestion

Repository metrics

Stars
 (5,549 stars)
PR merge metrics
 (Avg merge 5d 12h) (6 merged PRs in 30d)

Description

Hey, thank you for providing yet another nice tool for making the world a bit safer!

Since this tool is written in Rust and has quite a few direct and transitive dependencies, I was wondering if you could share some insight on ensuring you don't pull in malware by accident. This is a thing I'm struggling with a bit whenever I see some software is written in Rust or whenever I inherit Rust code to work on.

I know this is not an issue and I'm sorry for adding triage overhead, but seems to be the most appropriate place to ask such a question... well apart from a mailing list :D

Thank you, Jan

Contributor guide

Research direction
Investigate Rust dependency security best practices and supply chain attacks. Provide recommendations for vetting dependencies in Rust projects.
Tech stack
rust
Domain
security
Issue type
Research
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.
1-3 hours
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.
Clear
Prerequisites
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75