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 #792] [MERGED] NEW PLUGIN: added legal clause research plugin #ieeesoc #1176

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

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/792
Author: @pragnyanramtha
Created: 6/27/2025
Status: ✅ Merged
Merged: 7/1/2025
Merged by: @alterxyz

Base: main ← Head: plugin/legal_clause_researcher

📝 Commits (3)

📊 Changes

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

View changed files

➕ legal_clause_researcher/legal_clause_researcher.difypkg (+0 -0)

📄 Description

Plugin Submission Form

1. Metadata 

2. Submission Type

  • New plugin submission
  • Version update for existing plugin

3. Description

The Legal Clause Identifier Dify Plugin is a tool designed to analyze legal text and identify the presence of common contractual clauses. It integrates directly with the Thomson Reuters API, allowing your Dify applications to leverage advanced legal NLP capabilities to quickly find specific legal provisions within documents.

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

NO, this plugin does not collect any data but it does require a Thomson Reuters API and endpoint to fuction.
Refer to original repo to understand privacy policy and guide.

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/792 **Author:** [@pragnyanramtha](https://github.com/pragnyanramtha) **Created:** 6/27/2025 **Status:** ✅ Merged **Merged:** 7/1/2025 **Merged by:** [@alterxyz](https://github.com/alterxyz) **Base:** `main` ← **Head:** `plugin/legal_clause_researcher` --- ### 📝 Commits (3) - [`b415ce6`](https://github.com/langgenius/dify-plugins/commit/b415ce654928609a14aa30ab10544ae5d0b04f77) added legal clause research plugin - [`9337cb4`](https://github.com/langgenius/dify-plugins/commit/9337cb480d67b4245142b49d8ab1b5d125ce2511) final commit - [`e8d3150`](https://github.com/langgenius/dify-plugins/commit/e8d3150b467866f57646f9eabd17c710d9ea0381) added logo ### 📊 Changes **1 file changed** (+0 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `legal_clause_researcher/legal_clause_researcher.difypkg` (+0 -0) </details> ### 📄 Description # Plugin Submission Form ## 1. Metadata  - **Plugin Author**: pragnyan_ramtha - **Plugin Name**: legal clause research  - **Repository URL**: https://github.com/pragnyanramtha/dify-plugin-legal_clause_researcher.git ## 2. Submission Type - [X] New plugin submission - [ ] Version update for existing plugin ## 3. Description The Legal Clause Identifier Dify Plugin is a tool designed to analyze legal text and identify the presence of common contractual clauses. It integrates directly with the Thomson Reuters API, allowing your Dify applications to leverage advanced legal NLP capabilities to quickly find specific legal provisions within documents. ## 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 NO, this plugin does not collect any data but it does require a Thomson Reuters API and endpoint to fuction. Refer to original repo to understand privacy policy and guide. ### 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:50:16 -05:00
yindo closed this issue 2026-02-22 17:50:23 -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#1176
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?