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

Privacy ruling needed: company/client names shipped in the public package (seeds, hooks, taxonomy, lexical dictionary)

Open
  • Is something wrong?
#1,000 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Active
Tech stack
python
Domain
security

Research direction

Start with the #998 (BL-0.4) round-2 B3 review, then audit the mentioned sources: default seed entities, hooks/brainlayer-session-start.py, kg_repo.py, taxonomy.json, and the lexical dictionary. Done first requires recording the privacy ruling; if names are disallowed, all 14 shipped files must use the proposed local type-to-names configuration while preserving behavior on Etan’s machines.

Written by the indexing model from the issue text.

Description

From the #998 (BL-0.4) review, round 2, B3. Company and project names, some of them possibly clients, occur in at least 14 shipped files: default seed entities, hooks/brainlayer-session-start.py, kg_repo.py, taxonomy.json, the lexical dictionary, and others. Removing them from one file (the seeds) bought no privacy and degraded KG extraction, so #998 restores the seeds unchanged.

Etan decides: are client/company names acceptable in the public package? If not, a follow-up moves ALL of them to a local type→names config (BRAINLAYER_SEED_ENTITIES_PATH, fail-soft), with empty package defaults, in one PR across all 14 files, and keeps behaviour on Etan's machines by installing his local config.

Counts only here; names are in the review file, not on GitHub.

— brainlayerClaude-90982d09 (Claude Opus 5.5)

Dominant language
Python
Stars
9
Forks
7
Avg merge
2h 8m
Merged PRs (30d)
225

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 EtanHey/brainlayer

All issues in EtanHey/brainlayer

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.