mirror of https://git.openapi.site/https://github.com/desirecore/market.git synced 2026-10-21 07:24:00 +08:00

Files

Yige 8f7953948f fix: 补齐市场静态事实并保持旧客户端兼容 (#184 )

## 中文

补齐已有 owner 与已锁定上游内容可证明的许可证、技能类型和收录版本。保留 Anthropic Source Available
和其他附加条件，不把所有内容统一标为 MIT，不提升 listing-only 的安装准入。

README 保留最新的双语结构及以 manifest 为准的数量口径，增加静态目录不存访问量、下载量、评分或 Stars 的边界。

发布兼容性：**本 PR 不包含**两支团队新增的本地化字段，也不包含微信支付 `latestVersion:
1.0`；旧客户端会拒绝这些新字段，另以待发布 PR 保留，等匹配客户端发布后再合并。

验证：47 项目录校验测试、19 项 i18n 测试、5 项合集生成测试通过；完整目录/i18n/翻译新鲜度检查通过，6
个固定来源合集的生成检查通过，2 个浮动来源按既有规则明确跳过。发现并修复了生成器在 Windows 使用反斜杠造成的误报：输出改为 POSIX
路径，比较规则不放宽、不重写合集数据。

## English

Fill only license, type and listed-release facts supported by existing
owners or pinned upstream content. Preserve custom license restrictions
and acquisition eligibility. Keep the current bilingual README and
manifest-derived inventory; do not author usage analytics.

This PR deliberately excludes localized team fields and the two-part
WeChat Pay version that older clients reject. Those changes remain
pending a compatible client release.

Validation passes: 47 catalog-validator tests, 19 i18n tests, five
collection-generator tests, complete catalog and translation checks, and
generated inventory checks for six pinned collections. Two mutable
sources remain explicitly skipped. Fix Windows-generated path separators
without weakening comparison or changing declared children.

2026-09-22 01:09:03 +08:00

6.6 KiB

Raw Blame History

license, name, description, version, type, risk_level, status, tags, metadata, market

license

name

description

version

type

risk_level

status

Tianyancha Risk Query

L0: One-Sentence Summary

Input a company name, call the Tianyancha risk-info API, and return a structured risk profile (self / related-party / historical / warning, four categories).

L1: Overview

Data source: Tianyancha Open Platform risk/riskInfo/2.0
Auth: Token (Authorization header, without the Bearer prefix)
Invocation: HTTP GET (curl / HttpRequest tool)
Prerequisites: a valid Token with the risk API enabled

Credential Setup

This skill requires a Tianyancha Open Platform Token:

Register an enterprise account at the Tianyancha Open Platform
Purchase/enable an API package (risk/riskInfo/2.0 is authorized per package tier)
Export the token as the environment variable TIANYANCHA_TOKEN, or replace the {TIANYANCHA_TOKEN} placeholder below

L2: Procedure

1. Build the request

curl -s --max-time 30 --ssl-no-revoke \
  "https://open.api.tianyancha.com/services/open/risk/riskInfo/2.0?keyword={company-name-URL-encoded}" \
  -H "Authorization: ${TIANYANCHA_TOKEN}"

Parameters:

Param	Value	Notes
keyword	Company name (URL-encoded)	e.g. `华为技术有限公司`
Authorization	`{TIANYANCHA_TOKEN}`	Token in header, no `Bearer` prefix (adding one returns 300009)

2. Interpret the response

error_code == 0 and reason == "ok": success, extract result.riskList[]
error_code == 300009: account error — wrong token or a Bearer prefix was added
error_code == 300005: no permission for this API — the token does not cover it
error_code == 300008: missing parameter — check keyword

3. Response structure

result contains:

riskLevel: overall risk level
riskList[]: four risk categories (each with name / count / type / list[])

Category	type	Meaning
Self risk	1	The company's own judicial/business risks (court hearings / rulings / case filings / court announcements / judicial auctions)
Related-party risk	2	Risks of shareholders, executives, invested companies
Historical risk	3	Closed historical risks (historical filings / hearings / dishonest-debtor history)
Early warnings	0	Business-registration changes (investor / key-personnel / registered-capital / legal-representative changes, bankruptcy cases)

Each category's list[] holds sub-items with title (e.g. "开庭公告") / total / tag (warning / high-risk / info) / list[] (top details with id / title / desc / riskCount).

4. Normalized mapping

{
  "query_status": "success",
  "source": "tianyancha",
  "company_name": "{company name}",
  "risk_level": "{result.riskLevel}",
  "summary": {
    "self_risk_count": 3127,
    "related_risk_count": 1505,
    "history_risk_count": 9113,
    "warning_count": 815
  },
  "self_risks": [
    { "risk_type": "开庭公告", "count": 1501, "level": "警示", "title": "该公司起诉他人或公司的开庭公告", "detail_count": 1096 }
  ],
  "timestamp": "2026-08-31T21:00:00+08:00"
}

5. Due-diligence highlights

Prioritize as follows when composing the report:

High-risk entries (tag=高风险): e.g. "被执行人", "清算信息", "失信被执行人" — list as major risk items
Large warning counts (total > 100): e.g. 1,501 hearing announcements — list as judicial-activity indicators
Change warnings: recent investor / legal-representative / capital changes — list as business dynamics

Known Limitations

Tiered token authorization: APIs are authorized per package; unauthorized APIs return 300005 — full-dimension packages unlock business/shareholder/IP endpoints
QPS throttling: rate limits depend on the package; keep ≥1 s between calls
Large responses: big companies can return 98KB+ — extract summaries plus top-N details to keep context small

Troubleshooting

Code	Meaning	Fix
0	Success	—
300005	No permission for this API	Confirm the endpoint is covered by your package
300008	Missing parameter	Check the keyword parameter
300009	Account error	Wrong token / Bearer prefix / expired token — remove the prefix and retry; if still failing, update the token

6.6 KiB Raw Blame History Unescape Escape