langgenius/dify-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugins.git synced 2026-07-22 01:55:36 -04:00
Code Issues 119 Packages Projects Releases Wiki Activity

[PR #692] [MERGED] azure ai content safety container dify plugin v0.0.1 #1103

New Issue
Closed
opened 2026-02-22 17:48:15 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 17:48:15 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/692
Author: @HeyJiqingCode
Created: 6/15/2025
Status: ✅ Merged
Merged: 6/18/2025
Merged by: @crazywoola

Base: main ← Head: main

📝 Commits (4)

  • 12f9fcd azure ai content safety container dify plugin v0.0.1
  • f812e46 Merge branch 'langgenius:main' into main
  • 9462884 Merge branch 'langgenius:main' into main
  • b40351f update requirments

📊 Changes

1 file changed (+0 additions, -0 deletions)

View changed files

➕ heyjiqingcode/ai_content_safety/azure_ai_content_safety_container.difypkg (+0 -0)

📄 Description

Plugin Submission Form

1. Metadata

2. Submission Type

  • New plugin submission
  • Version update for existing plugin

3. Description

Overview

Azure AI Content Safety is an AI service that detects harmful user-generated and AI-generated content in applications and services. Azure AI Content Safety includes text and image APIs that allow you to detect material that is harmful.

Containers let you use a subset of the Azure AI Content Safety features in your own environment. With content safety containers, you can build a content safety application architecture optimized for both robust cloud capabilities and edge locality. Containers help you meet specific security and data governance requirements.

This is a Dify plugin that integrates with the Azure AI Content Safety Container API - Text to analyze text content for harmful material. The plugin can detect various types of harmful content including hate speech, violence, sexual content, and self-harm.

Features

  • Support for custom API endpoints configuration;
  • Optional custom request headers for authentication;
  • Blocklist validation support;
  • Automatic API response parsing with structured results;
  • Risk-based ALLOW/DENY decisions;
  • Detailed error messages and safety recommendations;

4. Checklist

  • I have read and followed the Publish to Dify Marketplace guidelines
  • I have read and comply with the Plugin Developer Agreement
  • I confirm my plugin works properly on both Dify Community Edition and Cloud Version
  • I confirm my plugin has been thoroughly tested for completeness and functionality
  • My plugin brings new value to Dify

5. Documentation Checklist

Please confirm that your plugin README includes all necessary information:

  • Step-by-step setup instructions
  • Detailed usage instructions
  • All required APIs and credentials are clearly listed
  • Connection requirements and configuration details
  • Link to the repository for the plugin source code

6. Privacy Protection Information

Based on Dify Plugin Privacy Protection Guidelines:

Data Collection

The Plugin runs in the local environment and does not send user data to the plugin developer's servers.

  • The Plugin does not control or influence the data processing policies of third-party APIs;
  • The Plugin does not share user data with any third parties;
  • All configuration information is stored in the user's Dify instance;
  • User-submitted text content is sent to the user's configured Azure AI Content Safety API endpoint for analysis;
  • For temporary data during text analysis exists only in memory and is not persistently stored;
  • API response results are used only to generate final safety detection results;

Privacy Policy

  • I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-plugins/pull/692 **Author:** [@HeyJiqingCode](https://github.com/HeyJiqingCode) **Created:** 6/15/2025 **Status:** ✅ Merged **Merged:** 6/18/2025 **Merged by:** [@crazywoola](https://github.com/crazywoola) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (4) - [`12f9fcd`](https://github.com/langgenius/dify-plugins/commit/12f9fcd66a7832e3707dc1628fec380d94889c88) azure ai content safety container dify plugin v0.0.1 - [`f812e46`](https://github.com/langgenius/dify-plugins/commit/f812e46e7be922d7070313dde95bc65b1982e0f5) Merge branch 'langgenius:main' into main - [`9462884`](https://github.com/langgenius/dify-plugins/commit/946288407e6adfaa51781c1b8d2ff68549a6d40d) Merge branch 'langgenius:main' into main - [`b40351f`](https://github.com/langgenius/dify-plugins/commit/b40351f038bc058d5a1eed48946b9743d33911cd) update requirments ### 📊 Changes **1 file changed** (+0 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `heyjiqingcode/ai_content_safety/azure_ai_content_safety_container.difypkg` (+0 -0) </details> ### 📄 Description # Plugin Submission Form ## 1. Metadata <!-- Please provide the following metadata of your plugin to make it easier for the reviewer to check the changes. - Plugin Author : The author of the plugin which is defined in your manifest.yaml - Plugin Name : The name of the plugin which is defined in your manifest.yaml - Repository URL: The URL of the repository where the source code of your plugin is hosted --> - **Plugin Author**: jiqing - **Plugin Name**: content-safety-container - **Repository URL**: https://github.com/HeyJiqingCode/AzureAIContentSafetyContainer-DifyPlugin ## 2. Submission Type - [x] New plugin submission - [ ] Version update for existing plugin ## 3. Description <!-- Please briefly describe the purpose of the new plugin or the updates made to the existing plugin --> ### Overview Azure AI Content Safety is an AI service that detects harmful user-generated and AI-generated content in applications and services. Azure AI Content Safety includes text and image APIs that allow you to detect material that is harmful. Containers let you use a subset of the Azure AI Content Safety features in your own environment. With content safety containers, you can build a content safety application architecture optimized for both robust cloud capabilities and edge locality. Containers help you meet specific security and data governance requirements. This is a Dify plugin that integrates with the [Azure AI Content Safety Container API - Text](https://learn.microsoft.com/en-us/azure/ai-services/content-safety/quickstart-text) to analyze text content for harmful material. The plugin can detect various types of harmful content including hate speech, violence, sexual content, and self-harm. ### Features - Support for custom API endpoints configuration; - Optional custom request headers for authentication; - Blocklist validation support; - Automatic API response parsing with structured results; - Risk-based ALLOW/DENY decisions; - Detailed error messages and safety recommendations; ## 4. Checklist - [x] I have read and followed the Publish to Dify Marketplace guidelines - [x] I have read and comply with the Plugin Developer Agreement - [x] I confirm my plugin works properly on both Dify Community Edition and Cloud Version - [x] I confirm my plugin has been thoroughly tested for completeness and functionality - [x] My plugin brings new value to Dify ## 5. Documentation Checklist Please confirm that your plugin README includes all necessary information: - [x] Step-by-step setup instructions - [x] Detailed usage instructions - [x] All required APIs and credentials are clearly listed - [x] Connection requirements and configuration details - [x] Link to the repository for the plugin source code ## 6. Privacy Protection Information Based on Dify Plugin Privacy Protection [Guidelines](https://docs.dify.ai/plugins/publish-plugins/publish-to-dify-marketplace/plugin-privacy-protection-guidelines): ### Data Collection <!-- Does your plugin collect any user personal data? If yes, please list what types of user personal data are being collected according to the Plugin Privacy Protection Guidelines (for example: Email address, IP address, Age, etc) --> The Plugin runs in the local environment and does not send user data to the plugin developer's servers. - The Plugin does not control or influence the data processing policies of third-party APIs; - The Plugin does not share user data with any third parties; - All configuration information is stored in the user's Dify instance; - User-submitted text content is sent to the user's configured Azure AI Content Safety API endpoint for analysis; - For temporary data during text analysis exists only in memory and is not persistently stored; - API response results are used only to generate final safety detection results; ### Privacy Policy - [x] I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-22 17:48:15 -05:00
yindo closed this issue 2026-02-22 17:48:19 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Plugin Request
Plugin Request
Plugin Request
bug
duplicate
enhancement
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugins#1103
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?