Project-data question labels: "Compiled Ass" header and a Yes option that says to choose No
Maintainers usually reply within 1 day
@khush2429 is already working on this.
Since Oct 21, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python
- Domain
- developer-experience
Research direction
Start in darnit_baseline/tools.py at _build_ask_user_params, especially the header formatting near line 999 and Yes option description near line 1020. Read the context definitions for has_compiled_assets and has_subprojects to see how their labels and hints are supplied. Done means the header is not cut off midword and the Yes option has a neutral description while the hint appears in the question text.
Written by the indexing model from the issue text.
Description
Two problems in _build_ask_user_params (darnit_baseline/tools.py):
- The header is
key.removeprefix("has_").removeprefix("is_").replace("_", " ").title()[:12](line 999), sohas_compiled_assetsis shown as "Compiled Ass". - For a yes/no question the Yes option's description is
definition.hint(line 1020). Forhas_subprojectsthat is "Set to false if this is a standalone project", shown next to the Yes button.
Fix: an explicit short header per context definition (or truncate at a word boundary), and a neutral description for Yes with the hint shown in the question text.
Drafted with Claude Code; reviewed and posted by me.
- Dominant language
- Python
- Stars
- 22
- Forks
- 27
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 50
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from darnitdevorg/darnit
-
module-core needs triage ux
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
darnitdevorg/darnit#648 ·
Maintainers usually reply within 1 day
-
ci needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
darnitdevorg/darnit#607 ·
Maintainers usually reply within 1 day
-
dependencies module-baseline needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
darnitdevorg/darnit#606 ·
Maintainers usually reply within 1 day
-
A test starts real Sigstore signing (interactive OIDC login) when the attestation extra is installedPossibly taken @mlieberman85 claimed this 3 days ago. Openmodule-baseline needs triage testing
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
darnitdevorg/darnit#604 ·
Maintainers usually reply within 1 day
-
`darnit validate` crashes on openssf-baseline.toml summarising levelsPossibly taken @i-am-paradox claimed this 8 days ago. Openinterface-cli module-core
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
darnitdevorg/darnit#589 · 1 comment ·
Maintainers usually reply within 1 day
All issues in darnitdevorg/darnit
Similar issues
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
yunaremaia/proto-drift#22 ·
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
yunaremaia/memwatch#96 ·
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 91/100
yunaremaia/ci-gate-watch#34 ·
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
yunaremaia/agent-capability-attestation#64 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 86/100
yunaremaia/agent-call-graph#43 ·
Maintainers usually reply within 1 day