New attribute : confidential indicator

Open
#59 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #66 by @deeeeeepesh — closed without merging

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Domain
ai, security

Research direction

No files, tests, or entry points are identified. First clarify whether the attribute should be a boolean, integer, or string, how its values are interpreted, and which metadata specification sections or examples must be updated; done means the representation and confidentiality behavior are documented and agreed.

Written by the indexing model from the issue text.

Description

Hello,
Sometimes, you may have a field that contains confidential information and the last thing you want is an LLM to use this field and the data to be exposed.
We can imagine :
-a boolean
-or a integer with a note from 1 to x
-or a string..

Best regards,

Simon

Dominant language
Python
Stars
2.7k
Forks
353
Avg merge
3d 19h
Merged PRs (30d)
86

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 apache/ossie

All issues in apache/ossie

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.