OWASP / OWASP/OpenCRE

Apply saved standards selection on search and explorer

Open
#1,082 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement not ready for development P2 untriaged
Dominant language
Python
Stars
180
Forks
137
Avg merge
3d 23h
Merged PRs (30d)
21

Description

Parent: #1079 · Depends on CRE-page apply-view ticket · Project: https://github.com/orgs/OWASP/projects/60

What

The same saved selection that filters CRE pages should apply to search results and explorer.

Without this, the feature feels broken: /cre/… is quiet, search and explorer still dump every standard.

Surfaces

  • Text search (/rest/v1/text_search / SearchName.tsx / DocumentNode)
  • Explorer (/explorer, including “show relevant standards” links that already emit applyFilters URLs)

Reuse the same mechanism as CRE pages (URL hydrate or include_only). Do not add a second persistence format.

Success

Logged-in user with a non-empty selection sees only those standards (plus OpenCRE) in search hits and explorer-linked CRE views, with the same “Show all” bypass as CRE pages.

Anonymous search/explorer stay unfiltered.

Out of scope

Map Analysis / ga_standards (separate ticket). Chat RAG (later ticket).

Contributor guide

Open the contributing guide

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.

Research direction

Trace the CRE-page saved-selection mechanism first, then inspect /rest/v1/text_search, SearchName.tsx, DocumentNode, and /explorer. Apply the existing URL hydrate or include_only path without introducing another persistence format. Done means logged-in users see only selected standards plus OpenCRE, Show all bypasses the filter, and anonymous search and explorer remain unfiltered.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, typescript
Domain
full-stack, search
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.