bump darko893/haunt to 0.1.1

[Darko893]

Plugin Submission

Plugin information

• Author: darko893
• Plugin name: haunt
• Version: 0.1.1
• Source repository: https://github.com/Darko893/dify-haunt
• Contact: support@hauntapi.com

Submission type

• New plugin
• Version update

What changed

Description and tags only. No functional change.

The listing was not findable for the words people search. Checked against the marketplace search API:

query	result
scrape	absent, 24 results
scraping	absent, 17 results
crawl	absent, 23 results
web scraping	rank 42 of 136

The description never used any of those words. It now leads with "Web scraping for AI apps" and adds the utilities tag alongside search, matching the other plugins in this category.

The crawl wording is deliberately scoped rather than claimed. The plugin extracts single pages and batches, it does not spider a whole site, and the description now says exactly that.

Diff between the 0.1.0 package and this one:

• changed: manifest.yaml, provider/haunt.yaml
• removed: tools/__pycache__/haunt_extract.cpython-312.pyc, which should not have been in 0.1.0
• byte-identical: all eight remaining files, including every .py

Risk level

• Low risk
• Medium risk
• High risk

Unchanged from 0.1.0. Medium because the plugin sends user-provided URLs and prompt text to a single fixed, documented HTTPS API (hauntapi.com), which fetches the page server-side. The plugin itself performs no browsing, no code execution, and no requests to any destination other than hauntapi.com.

Required checks

• I have read and followed the Marketplace submission requirements.
• I have read and comply with the Plugin Developer Agreement.
• I tested this plugin on Dify Community Edition and Dify Cloud, or documented any limitation below. See the note below: no new runtime testing was run for this version, because the runtime is byte-identical to the published 0.1.0.
• 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.

Security and privacy notes

Unchanged from 0.1.0. The tool accepts a user-provided URL, but the URL is sent as data to the fixed Haunt API endpoint (https://hauntapi.com/v1/extract) rather than fetched by the plugin. Outbound traffic goes to hauntapi.com only. Timeouts are set (120s tool, 15s credential check). The API key is held by Dify credentials and sent only in the X-API-Key header. Errors never echo the credential.

Testing note, stated plainly

I did not re-run the live extraction tests for this version, because no executable code changed. Every .py file in this package is byte-identical to the published 0.1.0, which is live with installs. The only differences are the two descriptor files and the removal of a stray __pycache__ entry.

One thing worth flagging for the packaging docs

Running dify-plugin-linux-amd64 plugin package against a git working directory sweeps the whole .git directory into the package: 58 entries and 104KB, including .git/config and .git/logs. That contradicts the submission rule about .git directories. This package was built with the same CLI from a clean copy containing only the ten runtime files, so it is 10 entries and 37KB. Might be worth a note in the packaging docs, or an exclude list in the CLI, since the default path produces a non-compliant package.