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

crypt.awk is not finished nor documented.

Open
#125 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
awk, bash

Research direction

Start by reviewing crypt.awk and the issue's proposal for a bash alternative, then identify what behavior is unfinished and how the utility is expected to be used. Confirm which implementation the project wants before changing it. Done should mean the chosen implementation is complete and its usage is documented in AsciiDoc.

Written by the indexing model from the issue text.

Description

crypt.awk is old, WIP, no documentation at all. awk is a weird choice anyway. If a bash solution is appropriate (you said you try to avoid it), I can come up with a pull request, documentation and all. Documentation is asciidoc, if that's a problem.

Dominant language
C
Stars
246
Forks
67
Avg merge
3d 12h
Merged PRs (30d)
1

Getting set up

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 void-linux/void-runit

All issues in void-linux/void-runit

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.