EFForg / EFForg/webrequest-tlsinfo-api
Add ct qualified?
Open
- Dominant language
- No language data
- Stars
- 16
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
We removed the SCT field, because it was a significant expansion of the implementation for unclear benefit; what do folks think about including ct qualified as a boolean?
Contributor guide
No contributing guide indexed for this repository
Research direction
No file, test, or entry point is identified. Start by reviewing the discussion about the removed SCT field and the proposed `ct qualified` boolean; the issue is ready only after its scope and expected behavior are decided.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100