[site-shot]

Plugin Submission

Plugin information

• Author: site-shot
• Plugin name: site_shot
• Version: 0.1.1
• Source repository: https://github.com/site-shot/dify-plugin-site-shot
• Contact: [email protected]

Submission type

• New plugin
• Version update

What changed

Documentation-only correction: 0.1.0 is now listed, but its bundled README still says it is not on Marketplace. Two README blocks now link the actual listing and distinguish Marketplace installation from local development. Only the top-level manifest version changes to 0.1.1; runtime, dependencies, privacy, assets and tool behavior remain unchanged.

Risk level

• Low risk
• Medium risk
• High risk

Security and privacy notes

The plugin sends a user-provided public page URL and provider API key to the fixed Site-Shot HTTPS API and returns validated image bytes. Security and privacy boundaries are unchanged.

Reviewer notes

There are no breaking changes or migration steps.
This release claims no new native acceptance: the retained installed-package/remote-debug checks were on version 0.1.0 in isolated Dify Community Edition 1.17.1. Dify Cloud, downstream vision-LLM use and long-page stitching remain untested. This factual installation correction is not a new functional capability. No new capture is part of this update.

Exact archive hash, immutable source commit, offline check results/warnings and all required-check checklist answers will be appended only after actual verification, without changes to the claims or scope above. Stop for new findings or terms.

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.

Local validation

Exact archive SHA256 a5d097223ba35057291fb492f2df3760647c46d961722a716b609c15982094f0, 16,345 bytes, 12 entries. Built with the existing official CLI under denied network access. Every archive member matches the source; only README.md and manifest.yaml differ from published 0.1.0.

The unchanged official Toolkit commit 57a21d1304b1108df3e6b90a15a4f5dd9f0915f9 runs offline with network denied. Three existing warning categories remain: a lexical Git checkout/payment match in local build instructions, an assembled fixed API hostname not inferred by the static access scan, and skipped online dependency vulnerability lookup. This is not a clean online vulnerability audit or new native installation test.

Exact source commit: site-shot/dify-plugin-site-shot@3995eeb .

[crazywoola]

Pre Check Plugin and PR Risk Label passed for this revision. Inspected the submitted package, documentation, and relevant source; this is a non-draft plugin submission with no Web3 functionality identified. This is an eligibility review, not a comprehensive security audit.