langgenius / langgenius/dify-plugins
Add Signet plugin — local-first cryptographic signing for agent workflows
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 554
- Forks
- 879
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 125
Description
Plugin: Signet
Cryptographic action receipts for Dify agent workflows. Ed25519 signing, hash-chained audit trail, offline verification.
Key difference from existing signing plugins: No API key, no SaaS, no network dependency. Signing keys and audit logs stay on your infrastructure.
Tools
| Tool | Description |
|---|---|
| Sign Action | Ed25519 sign any tool call, append to hash-chained audit log |
| Verify Receipt | Offline signature verification — no network needed |
| Audit Query | Query local audit trail by time range or tool name |
Setup
- Install plugin
- Optionally set a Key Name (default:
dify-agent) - No API keys, no accounts — auto-creates Ed25519 identity on first use
Why local-first matters
| Signet | SaaS signing | |
|---|---|---|
| API key required | No | Yes |
| Data leaves infrastructure | No | Yes |
| Offline verification | Yes | No |
| Key custody | You | Provider |
Compliance
Signed audit trails support SOC 2 (CC7.2, CC7.3), ISO 27001 (A.8.15), EU AI Act Article 12, and DORA. See full compliance mapping.
Source
- Plugin repo: https://github.com/Prismer-AI/dify-plugin-signet
- Signet: https://github.com/Prismer-AI/signet
- PyPI: signet-auth
Happy to submit a PR if there's interest.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the dify-plugin-signet repository and the linked Signet source, then inspect dify-plugins conventions for adding marketplace plugins. Use the listed Sign Action, Verify Receipt, and Audit Query tools as the proposed scope, and confirm what integration, packaging, and verification are required before the plugin can be listed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100