Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Security

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
github, rust
Domain
security

Research direction

No files, tests, or entry points are named. Start by tracing how GitHub webhook events select benchmark commits, then determine how branch and tag refs are represented and where arbitrary commit runs are accepted; done means untrusted webhook data cannot trigger runs for arbitrary commits.

Written by the indexing model from the issue text.

Description

Meta

Currently, the public IP has no domain, and therefore no ability to do HTTPS.

Therefore, GitHub has to send the WebHook secret in plain text, and it can (maybe, theoretically?) be sniffed.

So we should probably only allow running benchmarks on branches and tags, not arbitrary commits (as GitHub stores a fork’s PR commits in the parent repo)

Dominant language
Rust
Stars
4
Forks
0
Avg merge
4h 49m
Merged PRs (30d)
5

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scverse/benchmark

All issues in scverse/benchmark

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.