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

Mechanical trap-scanner and on-chain safety gate for Stellar assets. Classifies issuer capability from ledger flags, not reputation.

Is use-assay/Assay beginner-friendly?

In the last 30 days, use-assay/Assay merged 90 of 102 pull requests from outside contributors, and its maintainers usually reply within 2 days. 51 beginner-friendly issues are open now.

Stars
0
Forks
48
Open beginner issues
51
Indexed issues
317
Avg merge
1d 17h
Merged PRs (30d)
94
Dominant language
Go
License
Apache-2.0
Last GitHub push
Sep 30, 2026
Latest indexed
Sep 27, 2026
Contributing guide
Contributing guide
Code of conduct
Code of conduct
Beginner labels
good first issue help wanted

How to contribute to use-assay/Assay

  1. Read the contributing guide first: it says how the maintainers want changes proposed, tested and reviewed.
  2. Read its code of conduct: it covers issues and pull requests as well as chat.
  3. Your contributions will be published under the project's Apache-2.0 license.
  4. Pick one of the 51 open beginner-friendly issues below and comment that you want to work on it before you start.

Issues somebody may already be working on are listed last. List everything by date

  • Offline verification bundle: archive the exact source bytes behind each attestation
    Open
    area:data area:security difficulty:hard needs-maintainer-review Stellar Wave

    Difficulty 5/5 Over a week Newbie friendliness 8/100

    use-assay/Assay#465 · 1 comment ·

    Maintainers usually reply within 2 days

  • `assay diff`: compare two saved reports
    Open
    area:cli area:temporal difficulty:hard Stellar Wave

    Difficulty 4/5 3-5 days Newbie friendliness 35/100

    use-assay/Assay#464 · 1 comment ·

    Maintainers usually reply within 2 days

  • Translate key reader-facing docs into French and Spanish
    Open
    area:docs difficulty:medium Stellar Wave

    Difficulty 3/5 1-2 days Newbie friendliness 62/100

    use-assay/Assay#462 · 1 comment ·

    Maintainers usually reply within 2 days

  • golangci-lint: enable `errorlint` and `wrapcheck`
    Open
    area:testing difficulty:medium Stellar Wave

    Difficulty 3/5 Half a day Newbie friendliness 62/100

    use-assay/Assay#459 · 1 comment ·

    Maintainers usually reply within 2 days

  • Research: measure how often scans are undetermined over a week
    Open
    area:ops area:research difficulty:medium Stellar Wave

    Difficulty 4/5 Over a week Newbie friendliness 45/100

    use-assay/Assay#454 · 1 comment ·

    Maintainers usually reply within 2 days

  • Research: agreement between Assay severity and StellarExpert rating
    Open
    area:research difficulty:medium Stellar Wave

    Difficulty 3/5 1-2 days Newbie friendliness 50/100

    use-assay/Assay#453 · 1 comment ·

    Maintainers usually reply within 2 days

  • CI: fail when a Go package is missing from the architecture map
    Open
    area:docs area:testing difficulty:medium Stellar Wave

    Difficulty 3/5 1-2 days Newbie friendliness 45/100

    use-assay/Assay#452 · 1 comment ·

    Maintainers usually reply within 2 days

  • Architecture doc: package map omits five packages
    Open
    area:docs difficulty:easy good first issue Stellar Wave

    Difficulty 2/5 1-3 hours Newbie friendliness 82/100

    use-assay/Assay#451 · 1 comment ·

    Maintainers usually reply within 2 days

  • Session notes: add the 2026-10 sessions
    Open
    area:docs difficulty:easy good first issue Stellar Wave

    Difficulty 2/5 1-3 hours Newbie friendliness 70/100

    use-assay/Assay#448 ·

    Maintainers usually reply within 2 days

  • `docs/integrating.md`: add a section on handling the five gate errors
    Open
    area:contracts area:docs difficulty:easy good first issue Stellar Wave

    Difficulty 2/5 1-3 hours Newbie friendliness 72/100

    use-assay/Assay#447 ·

    Maintainers usually reply within 2 days

  • Structured logs: test that issuer strings cannot forge log entries
    Open
    area:security area:testing difficulty:medium Stellar Wave

    Difficulty 3/5 Half a day Newbie friendliness 58/100

    use-assay/Assay#445 ·

    Maintainers usually reply within 2 days

  • Add `.editorconfig`
    Open
    area:contributor-experience difficulty:easy good first issue Stellar Wave

    Difficulty 2/5 1-3 hours Newbie friendliness 70/100

    use-assay/Assay#442 ·

    Maintainers usually reply within 2 days

  • Runbook: responding to a reproducibility-job mismatch
    Open
    area:docs area:ops difficulty:easy good first issue Stellar Wave

    Difficulty 3/5 1-2 days Newbie friendliness 45/100

    use-assay/Assay#440 ·

    Maintainers usually reply within 2 days

  • Issuer watcher: detect flag changes for attested issuers
    Open
    area:ops area:temporal difficulty:hard Stellar Wave

    Difficulty 4/5 3-5 days Newbie friendliness 30/100

    use-assay/Assay#439 ·

    Maintainers usually reply within 2 days

  • CI: dry-run the attested set on scanner changes and diff it
    Open
    area:ops area:testing difficulty:medium Stellar Wave

    Difficulty 4/5 3-5 days Newbie friendliness 30/100

    use-assay/Assay#438 ·

    Maintainers usually reply within 2 days

  • API: version the UI's API calls and the API itself together
    Open
    area:api area:ui difficulty:easy good first issue Stellar Wave

    Difficulty 3/5 1-2 days Newbie friendliness 45/100

    use-assay/Assay#431 ·

    Maintainers usually reply within 2 days

  • API: machine-readable error codes in error bodies
    Open
    area:api difficulty:medium Stellar Wave

    Difficulty 4/5 3-5 days Newbie friendliness 35/100

    use-assay/Assay#427 ·

    Maintainers usually reply within 2 days

  • UI: accessibility pass (labels, live region, focus)
    Open
    area:ui difficulty:medium Stellar Wave

    Difficulty 3/5 Half a day Newbie friendliness 72/100

    use-assay/Assay#421 ·

    Maintainers usually reply within 2 days

  • UI: deep-link a scan with `?asset=`
    Open
    area:ui difficulty:easy good first issue Stellar Wave

    Difficulty 3/5 Half a day Newbie friendliness 60/100

    use-assay/Assay#420 ·

    Maintainers usually reply within 2 days

  • Asset lists: cache fetched lists with honest staleness
    Open
    area:mechanics difficulty:medium Stellar Wave

    Difficulty 3/5 1-2 days Newbie friendliness 55/100

    use-assay/Assay#408 ·

    Maintainers usually reply within 2 days

  • Report StellarExpert's asset rating as context only (follow-up guardrails for #6)
    Open
    area:mechanics area:testing difficulty:easy good first issue Stellar Wave

    Difficulty 2/5 1-3 hours Newbie friendliness 30/100

    use-assay/Assay#401 ·

    Maintainers usually reply within 2 days

  • Add a `-horizon` flag to the CLI
    Open
    area:cli difficulty:easy good first issue Stellar Wave

    Difficulty 2/5 1-3 hours Newbie friendliness 72/100

    use-assay/Assay#398 ·

    Maintainers usually reply within 2 days

  • Temporal: make de-escalation a first-class transition
    Open
    area:security area:temporal difficulty:hard Stellar Wave

    Difficulty 4/5 3-5 days Newbie friendliness 30/100

    use-assay/Assay#388 ·

    Maintainers usually reply within 2 days

  • Network-wide census of issuer flag changes
    Open
    area:research area:temporal difficulty:hard Stellar Wave

    Difficulty 4/5 3-5 days Newbie friendliness 15/100

    use-assay/Assay#386 ·

    Maintainers usually reply within 2 days

  • Publish the eval dataset as a versioned release artifact with checksums
    Open
    area:data difficulty:easy good first issue Stellar Wave

    Difficulty 3/5 1-2 days Newbie friendliness 30/100

    use-assay/Assay#385 ·

    Maintainers usually reply within 2 days

  • SEP-1: normalise trailing dots, ports and case in `home_domain`
    Open
    area:mechanics difficulty:easy good first issue Stellar Wave

    Difficulty 3/5 Half a day Newbie friendliness 62/100

    use-assay/Assay#374 ·

    Maintainers usually reply within 2 days

  • Publish a reusable `assay-gate` Rust crate for integrators
    Possibly taken @OlayiwolaSherrifSalawu claimed this today. Open
    area:contracts difficulty:hard Stellar Wave

    Difficulty 4/5 3-5 days Newbie friendliness 22/100

    use-assay/Assay#469 · 3 comments · 1 assignee ·

    Maintainers usually reply within 2 days

  • Formal grammar and conformance suite for the evidence encoding
    Possibly taken @OlayiwolaSherrifSalawu claimed this today. Open
    area:security area:testing difficulty:hard Stellar Wave

    Difficulty 5/5 Over a week Newbie friendliness 22/100

    use-assay/Assay#468 · 3 comments · 1 assignee ·

    Maintainers usually reply within 2 days

  • Holder portfolio exposure: scan every asset an account holds
    Possibly taken @OlayiwolaSherrifSalawu claimed this today. Open
    area:api area:mechanics difficulty:hard Stellar Wave

    Difficulty 4/5 3-5 days Newbie friendliness 25/100

    use-assay/Assay#467 · 3 comments · 1 assignee ·

    Maintainers usually reply within 2 days

  • Record-and-replay for live scans
    Possibly taken @OlayiwolaSherrifSalawu claimed this today. Open
    area:mechanics area:testing difficulty:hard Stellar Wave

    Difficulty 4/5 3-5 days Newbie friendliness 30/100

    use-assay/Assay#466 · 3 comments · 1 assignee ·

    Maintainers usually reply within 2 days

  • End-to-end test on a local standalone network: scan, attest, gate
    Possibly taken @AllysiadevOps claimed this today. Open
    area:contracts area:ops area:testing difficulty:hard Stellar Wave

    Difficulty 4/5 3-5 days Newbie friendliness 25/100

    use-assay/Assay#463 · 1 comment ·

    Maintainers usually reply within 2 days

  • Document the `.github/ISSUE_TEMPLATE` choices in CONTRIBUTING
    Possibly taken @Anichris-koded claimed this today. Open
    area:contributor-experience area:docs difficulty:easy good first issue Stellar Wave

    Difficulty 1/5 1-3 hours Newbie friendliness 72/100

    use-assay/Assay#461 · 1 comment ·

    Maintainers usually reply within 2 days

  • CODEOWNERS: cover `assay-contracts/**/test_snapshots`
    Possibly taken @emarkees claimed this today. Open
    area:contributor-experience difficulty:easy good first issue Stellar Wave

    Difficulty 2/5 1-3 hours Newbie friendliness 62/100

    use-assay/Assay#460 · 1 comment ·

    Maintainers usually reply within 2 days

  • Go: enable `-race` and `-shuffle=on` locally via `make test`
    Possibly taken @Anichris-koded claimed this today. Open
    area:testing difficulty:easy good first issue Stellar Wave

    Difficulty 3/5 Half a day Newbie friendliness 62/100

    use-assay/Assay#458 · 1 comment ·

    Maintainers usually reply within 2 days

  • Makefile: `make attest` fails unclearly when the `stellar` CLI is missing
    Possibly taken @facelessdevhack claimed this 1 day ago. Open
    area:contributor-experience bug difficulty:easy good first issue Stellar Wave

    Difficulty 2/5 1-3 hours Newbie friendliness 75/100

    use-assay/Assay#457 · 1 comment ·

    Maintainers usually reply within 2 days

  • Examples: a script that verifies every live attestation end to end
    Possibly taken @demola13777 claimed this today. Open
    area:cli area:docs difficulty:medium Stellar Wave

    Difficulty 3/5 1-2 days Newbie friendliness 55/100

    use-assay/Assay#456 · 1 comment ·

    Maintainers usually reply within 2 days

  • Research: what a third-party verifier actually needs, tested with someone new
    Possibly taken @Anichris-koded claimed this today. Open
    area:docs area:research difficulty:medium Stellar Wave

    Difficulty 3/5 1-2 days Newbie friendliness 45/100

    use-assay/Assay#455 · 1 comment ·

    Maintainers usually reply within 2 days

  • Pipeline doc and architecture doc: remove overlap
    Possibly taken @Donaldhemen claimed this today. Open
    area:docs difficulty:easy good first issue Stellar Wave

    Difficulty 2/5 1-3 hours Newbie friendliness 68/100

    use-assay/Assay#450 · 2 comments ·

    Maintainers usually reply within 2 days

  • Debugging guide: add a worked example of an `undetermined` verdict
    Possibly taken @Somtexzy claimed this 1 day ago. Open
    area:docs difficulty:easy good first issue Stellar Wave

    Difficulty 1/5 1-3 hours Newbie friendliness 85/100

    use-assay/Assay#449 ·

    Maintainers usually reply within 2 days

  • Document the `holder=` trustline query in `docs/api.md` and OpenAPI
    Possibly taken @shekwolonathanielbala-cyber claimed this today. Open
    area:api area:docs difficulty:easy good first issue Stellar Wave

    Difficulty 2/5 1-3 hours Newbie friendliness 72/100

    use-assay/Assay#446 ·

    Maintainers usually reply within 2 days

  • SECURITY.md: supported-versions section
    Possibly taken @demola13777 claimed this today. Open
    area:docs area:security difficulty:easy good first issue Stellar Wave

    Difficulty 1/5 Under an hour Newbie friendliness 70/100

    use-assay/Assay#444 ·

    Maintainers usually reply within 2 days

  • PR template: checklist items for preimage and ABI changes
    Possibly taken @demola13777 claimed this today. Open
    area:contributor-experience difficulty:easy good first issue Stellar Wave

    Difficulty 1/5 Under an hour Newbie friendliness 85/100

    use-assay/Assay#443 ·

    Maintainers usually reply within 2 days

  • CONTRIBUTING: a "first 15 minutes" walkthrough
    Possibly taken @Aonlike claimed this today. Open
    area:contributor-experience difficulty:easy good first issue Stellar Wave

    Difficulty 2/5 1-3 hours Newbie friendliness 62/100

    use-assay/Assay#441 ·

    Maintainers usually reply within 2 days

  • Implement `assay-attester --dry-run` (no key material)
    Possibly taken @Aonlike claimed this today. Open
    area:cli area:ops difficulty:hard Stellar Wave

    Difficulty 4/5 3-5 days Newbie friendliness 32/100

    use-assay/Assay#437 ·

    Maintainers usually reply within 2 days

  • Attestation run record: define the schema
    Possibly taken @Somtexzy claimed this 1 day ago. Open
    area:ops difficulty:medium Stellar Wave

    Difficulty 3/5 1-2 days Newbie friendliness 45/100

    use-assay/Assay#436 ·

    Maintainers usually reply within 2 days

  • Health: report the attested set's staleness from `/readyz`
    Possibly taken @Donaldhemen claimed this today. Open
    area:api area:ops difficulty:medium Stellar Wave

    Difficulty 3/5 1-2 days Newbie friendliness 42/100

    use-assay/Assay#435 ·

    Maintainers usually reply within 2 days

  • Release workflow building CLI binaries for Linux, macOS and Windows
    Possibly taken @Donaldhemen claimed this today. Open
    area:ops difficulty:medium Stellar Wave

    Difficulty 3/5 Half a day Newbie friendliness 42/100

    use-assay/Assay#434 ·

    Maintainers usually reply within 2 days

  • Decide whether to host a public `assay serve` instance
    Possibly taken @demola13777 claimed this today. Open
    area:ops area:research difficulty:medium needs-maintainer-review Stellar Wave

    Difficulty 4/5 1-2 days Newbie friendliness 22/100

    use-assay/Assay#433 ·

    Maintainers usually reply within 2 days

  • Container image for `assay serve`
    Possibly taken @Aycode01 claimed this today. Open
    area:ops difficulty:medium Stellar Wave

    Difficulty 3/5 1-2 days Newbie friendliness 55/100

    use-assay/Assay#432 ·

    Maintainers usually reply within 2 days

  • API: `Cache-Control` and `Age` headers reflecting cached evidence
    Possibly taken @Donaldhemen claimed this today. Open
    area:api difficulty:easy good first issue Stellar Wave

    Difficulty 3/5 Half a day Newbie friendliness 45/100

    use-assay/Assay#430 ·

    Maintainers usually reply within 2 days

Showing the newest 100

This page lists what was indexed most recently. Advanced filter has the whole inventory, narrowed by language, difficulty and how long a task takes.

Open advanced filter

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.