Skip to content

Add secondstudio/second_studio 0.0.1 - #3857

Open
psulli007 wants to merge 1 commit into
langgenius:mainfrom
psulli007:secondstudio-second_studio-0.0.1
Open

psulli007 wants to merge 1 commit into
langgenius:mainfrom
psulli007:secondstudio-second_studio-0.0.1

Conversation

@psulli007

@psulli007 psulli007 commented Nov 19, 2026 •

Copy link
Copy Markdown

Plugin Submission

Plugin information

This pull request changes only secondstudio/second_studio/second_studio-0.0.1.difypkg. The plugin source, README, PRIVACY.md, screenshots, and assets live in the public source repository linked above, which is the source of record.

Submission type

  • New plugin
  • Version update

What changed

This is a new tool plugin for Second Studio. In a Dify workflow or agent it can:

  • Create an explainer video from a public product page (Create video).
  • Read job status (Get job).
  • Return the finished video URL (Get video).

Marketplace tags in manifest.yaml: videos, productivity, business.

Create video can also be run with estimate: true to quote the credit cost without starting a job.

The plugin talks only to https://secondstudio.dev. The user's Second Studio API key is stored as a Dify secret input and sent as a Bearer token. Product page URLs and optional style URLs are sent to Second Studio as API fields; the plugin does not fetch those URLs itself.

Tested on Dify Community Edition 1.20.0 (local Docker images langgenius/dify-api:1.20.0 and langgenius/dify-web:1.20.0). Dify Cloud was not tested.

Risk level

  • Low risk
  • Medium risk
  • High risk

Medium risk: the plugin sends user-provided URLs and optional brief text to Second Studio, and Create video starts a paid render on that account.

Required checks

  • I have read and followed the Marketplace submission requirements.
  • I have read and comply with the Plugin Development Guidelines.
  • I tested this plugin on Dify Community Edition and Dify Cloud, or documented any limitation below.
  • The package contains only files needed at runtime.
  • The package does not contain secrets, local credentials, .env files, .git directories, virtual environments, caches, logs, or IDE files.
  • The package does not contain executables or bundled binaries, or I explained why they are required below.
  • The plugin README includes setup steps, usage instructions, required APIs or credentials, connection requirements, and the source repository link.
  • The plugin includes PRIVACY.md or a hosted privacy policy, and manifest.yaml references it.
  • All user-facing text is primarily in English, with any localized README files following the i18n guidance.

Limitation: Dify Cloud was not tested. Community Edition 1.20.0 was tested, including a local package install, credential setup (GET /v1/me), an estimate-only Create video call, a successful published workflow run of Get video, and a successful explainer render.

Security and privacy notes

  • User-provided product_url and optional style_url are sent to Second Studio. The plugin does not fetch arbitrary URLs, follow redirects to other hosts, proxy traffic, or crawl the public web itself.
  • Create video is a write action on the user's Second Studio account. It can spend credits and start a render. estimate: true quotes a price and does not start a job. Get job and Get video are reads.
  • The plugin connects only to https://secondstudio.dev, as declared in manifest.yaml network.domains.
  • The API key is a secret input. It is sent in the Authorization header and is not included in tool output or error text.
  • The plugin does not execute commands or code, run SQL, access a filesystem, automate a browser, or handle health, financial, biometric, children, or other sensitive personal data.

Local validation

Ran the Marketplace toolkit validators from langgenius/dify-marketplace-toolkit (current main) and the official plugin daemon dify-plugin-linux-amd64 (v0.6.15), against secondstudio/second_studio/second_studio-0.0.1.difypkg.

python3 validator/validate-difypkg.py second_studio-0.0.1.difypkg \
  --pr-body-file pr-body.md --output-dir /tmp/ss-dify-validation
# exit 0

python3 validator/check-pr-body.py --pr-body-file pr-body.md
# PR body check passed

python3 validator/check-pr-review-notes.py --pr-body-file pr-body.md
# PR review note check passed

timeout 300 python3 uploader -d unpacked_plugin -t placeholder \
  --plugin-daemon-path dify-plugin-linux-amd64 \
  -u https://marketplace.dify.ai -f --test
# plugin packaged successfully; Skip uploading package in testing; exit 0
## Local DIFYPKG Validation Summary

- Report directory: /tmp/ss-dify-validation
- Blocking failures: 0
- Warning categories: 4
- Environment/check execution failures: 0

| Check | Type | Status | Findings |
|---|---|---|---|
| `package_contents` | blocking | PASS | No findings. |
| `package_secrets` | blocking | PASS | No findings. |
| `package_binaries` | blocking | PASS | No findings. |
| `manifest_metadata` | blocking | PASS | No findings. |
| `readme_metadata` | blocking | PASS | No findings. |
| `package_dependencies` | blocking | PASS | No findings. |
| `python_compile` | blocking | PASS | No findings. |
| `python_safety` | warning | PASS | No findings. |
| `prohibited_financial_activity` | warning | PASS | strong manual review required: official Dify Marketplace guidelines prohibit financial transactions, including payments, asset transfers, and token transfers |
| `access_domains` | warning | PASS | detected 1 outbound domain(s) by static scan: |
| `dependency_vulnerabilities` | warning | PASS | dependency source: requirements.txt (0 pinned, 1 unpinned) |
| `sensitive_capabilities` | blocking | PASS | sensitive capability signals detected; reviewer should verify PR disclosure: |

### Skipped checks
- PR title/body language and template checks require GitHub PR metadata
- Marketplace duplicate-version check requires Marketplace/PR workflow context
- plugin install and upload-package tests are not run by this local validator

### Warnings for review
- prohibited_financial_activity:
  - strong manual review required: official Dify Marketplace guidelines prohibit financial transactions, including payments, asset transfers, and token transfers
  - payment processing: tools/get_job.yaml:36: refunded:
  - payment processing: tools/get_video.yaml:64: refunded:
  - payment processing: lib/flows.py:181: "refunded": view["refunded"],
  - payment processing: lib/flows.py:272: "refunded": job.get("refunded"),
- access_domains:
  - detected 1 outbound domain(s) by static scan:
  -   secondstudio.dev [domain] (lib/client.py:11, lib/client.py:85)
  - 1 of 1 outbound call site(s) build their address at runtime; those hosts cannot be extracted statically
- dependency_vulnerabilities:
  - dependency source: requirements.txt (0 pinned, 1 unpinned)
  - 1 dependency(ies) have no exact version and were not checked: dify-plugin
  - no pinned dependencies to look up
- sensitive_capabilities:
  - sensitive capability signals detected; reviewer should verify PR disclosure:
  - arbitrary network requests: lib/client.py:66: req = urllib.request.Request(url, data=data, method=method)

Packaging --test output (excerpt):

v0.6.15
INFO plugin packaged successfully output_path=temp.difypkg
Security scan: 1 domain(s), 0 undeclared, 1/1 runtime-constructed call site(s); dependencies=ok (0 vulnerability findings); capabilities=1 categor(ies)
!!! Skip uploading package in testing

Reviewer notes

  • Create video wait_seconds and Get video timeout_seconds are capped at 180 seconds. If a render is still running, Get video returns status: running (or another live status) instead of waiting further. Call Get video again with the same job id.
  • The local validator flags the job field refunded as payment processing. That field is only a status flag from Second Studio: it is true when a failed render is credited back. This plugin does not process payments, transfers, or tokens.
  • The validator also flags urllib.request.Request as an arbitrary network request. The URL is always https://secondstudio.dev/v1 plus a fixed path. The request host is not taken from user input.
  • requirements.txt pins the Dify plugin SDK as dify_plugin>=0.11.0,<0.12.0 (range, not an exact pin).
  • During Community Edition testing, a 15 second explainer failed at script writing with brief beat b3 is mapped but its content is not present and was refunded. A 60 second explainer, which is the tool default, completed successfully. Short 15 second explainers can fail depending on the page brief.

Screenshots

From local testing on Dify Community Edition 1.20.0. Setup and a successful Logs run:

Plugin installed

Provider setup

Workflow

Successful run

The screenshot files are in the source repository at _assets/screenshots/. They are excluded from the .difypkg by .difyignore.

@github-actions github-actions Bot added the risk: medium Medium-risk Marketplace submission label Nov 19, 2026
@crazywoola

crazywoola commented Nov 20, 2026 •

Copy link
Copy Markdown
Member

Thank you for the Second Studio submission. The Pre Check Plugin run stops at Get PR Path because it permits only .difypkg file changes in a submission PR. This PR also adds source, documentation, screenshots, and assets alongside the package. Please keep those files in the linked source repository and update this PR to contain only secondstudio/second_studio/second_studio-0.0.1.difypkg.

The Governance run also reports that manifest.yaml has no tags list, both in the source and the package. Please add a non-empty list using the repository's controlled vocabulary, rebuild the package, and obtain fresh successful validations. The package validation steps were skipped after the Pre Check blocker.

@psulli007
psulli007 force-pushed the secondstudio-second_studio-0.0.1 branch from 092ec92 to f811a85 Compare November 20, 2026 13:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk: medium Medium-risk Marketplace submission

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants