Skip to content

Add Amap Tools 0.0.3 tool plugin (corporate entity migration) - #3873

Open
Ellanzhang1989 wants to merge 2 commits into
langgenius:mainfrom
Ellanzhang1989:add-amap_tools-0.0.3-corp
Open

Ellanzhang1989 wants to merge 2 commits into
langgenius:mainfrom
Ellanzhang1989:add-amap_tools-0.0.3-corp

Conversation

@Ellanzhang1989

@Ellanzhang1989 Ellanzhang1989 commented Nov 21, 2026 •

Copy link
Copy Markdown

Plugin Submission

Plugin information

Submission type

  • New plugin
  • Version update

What changed

Amap Tools — China location tools (geocoding, reverse geocoding, POI keyword
search, city weather) via the Amap (Gaode) Web Service API, with the user's
own API key.

This is the corporate-entity version of the plugin currently published
under the personal account ellan1989 (marketplace page:
https://marketplace.dify.ai/plugin/ellan1989/amap_tools, original PRs #3438
and #3547). Following the Dify Community Operations team's guidance (Sherry
Zhao, email thread on the partner application by Saide Technology), we are migrating the plugin to our corporate account. The team
confirmed the system does not support author ownership transfer, and
recommended resubmitting under the corporate account and then retiring the
personal-account listing. We will request the takedown of the personal
version once this one is live.

The plugin itself is functionally identical to #3547 (0.0.2); changes are
author/org fields, contact email (zhanglinlin@saidetech.com), source repo,
and version bump to 0.0.3.

Risk level

  • Low risk
  • Medium risk
  • High risk

Read-only GET requests to a single declared API domain
(restapi.amap.com in manifest.yaml network.domains); no file, shell,
database, or arbitrary-URL capabilities. Independent third-party integration
with Amap, clearly labeled as not affiliated with Amap in the README.

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.
  • 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

None. The plugin forwards only user-provided input (address, coordinates,
keyword, adcode) to the official endpoint https://restapi.amap.com and
returns the result; nothing is stored or sent anywhere else. Users bring
their own Amap API key (free tier available). See PRIVACY.md.

Local validation

Ran the official validator from langgenius/dify-marketplace-toolkit on the
exact uploaded archive:

python validator/validate-difypkg.py ellanzhang1989/amap_tools/amap_tools-0.0.3.difypkg --output-dir ./validation-report

Result: 0 blocking failures — all blocking checks PASS. The package
includes the explicit provider tools list and JSON-Schema output_schema
format introduced in #3547, which resolved the earlier production
"package decode failed" issue (see #3529).

Reviewer notes

  • Migration from ellan1989 to the corporate account ellanzhang1989
    (Saide Technology), per Community Operations guidance; the personal-account
    listing will be retired after this one is live.
  • Dependencies pinned (dify-plugin==0.10.2, httpx==0.28.1).

@github-actions github-actions Bot added the risk: low Low-risk Marketplace submission label Nov 21, 2026
@crazywoola

Copy link
Copy Markdown
Member

The Pre Check Plugin run failed the PR body check: it reported “PR title/body primary content must be English (found 4 CJK characters).” The current description still includes the Chinese company name alongside its English name. Please adjust that text to satisfy the validator, then ensure a fresh validation succeeds. The package checks in that run passed; this is a PR-body failure.

@Ellanzhang1989

Copy link
Copy Markdown
Author

Apologies — the body contained the company's Chinese name alongside its English name, which tripped the English-only PR text check. The body has been rewritten in pure English (verified locally with check-pr-body.py, 0 CJK characters). Could you please re-run the Pre Check workflow on this revision? No changes to the package itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

risk: low Low-risk Marketplace submission

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants