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

feat(detection): add detector-only mode

Open
#280 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #283 by @afourniernv — closed without merging

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python

Research direction

Trace the workflow construction, model alias validation, excluded-label handling, telemetry, serialization, and public API propagation entry points mentioned in the issue. Add coverage for detector-only behavior and skipped refinement models, then verify the finalized schema and documented speed-versus-quality tradeoff; benchmark accuracy and latency separately before production readiness.

Written by the indexing model from the issue text.

Description

Priority

Low

Problem

The detection pipeline always performs GLiNER detection, LLM validation, and LLM augmentation. Latency-sensitive callers cannot explicitly choose the raw detector result even when they accept lower precision and recall.

Proposed solution

Add an opt-in detector-only mode that:

  • runs the configured GLiNER detector;
  • skips validator and augmenter model calls;
  • finalizes the same entity/result schema;
  • marks skipped refinement models as not applicable in telemetry; and
  • documents that this is a speed-versus-quality choice, not a production privacy guarantee.

Alternatives considered

  • Configure no validator/augmenter aliases: current validation treats those roles as required and the workflow still builds refinement columns.
  • Implement the fast path only in a downstream Relay plugin: that would depend on Anonymizer internals and duplicate detection finalization.

Validation expectation

Unit tests should cover workflow construction, model alias validation, excluded labels, telemetry, serialization, and public API propagation. Before calling the mode production-ready, benchmark its accuracy and latency on representative data; early live testing showed both missed detections and over-redaction.

Dominant language
Python
Stars
129
Forks
21
Avg merge
2d 6h
Merged PRs (30d)
21

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 NVIDIA-NeMo/Anonymizer

All issues in NVIDIA-NeMo/Anonymizer

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.