dotnet / dotnet/aspnetcore

Components.AI: Define link and HTML safety for model-generated rich content

Open
#68,427 0 comments 0 reactions 0 assignees View on GitHub
area-blazor cost: S Priority:0 Security
Dominant language
C#
Stars
38.4k
Forks
10.9k
Avg merge
2d 5h
Merged PRs (30d)
276

Description

### Is your feature request related to a problem? Please describe the problem.

Model-generated links and HTML-like nodes create navigation, opener, and injection risks without a documented policy.

### Describe the solution you'd like

Define and enforce link target/`rel` defaults, supported URI schemes, HTML-node behavior, and the sanitization responsibility boundary between parser, application, and renderer. Document unsafe extension points clearly.

### Additional context

Leaf task for #68227 requirement J5.

Contributor guide

Open the contributing guide

Research direction

Start with parent requirement #68227, requirement J5, and trace where parser, application, and renderer responsibilities are defined. Determine the existing entry points and tests for model-generated links and HTML-like nodes; done means the safety policy is enforced, unsafe extension points are documented, and coverage verifies the stated defaults and supported schemes.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
security, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.