Caveat verdict

qianfan-deepresearch

deepresearch-conversation

88
🟢 Trusted
No high-risk patterns surfaced by the deep scan — automated capability review, not behavioral proof.

Calls Baidu Qianfan DeepResearch API using the user's own QIANFAN_API_KEY from environment; credential_access is legitimately used to read the user-configured API key for the stated deep research purpose.

⚠ Flagged for review — coarse, uncorroborated signal, not a confirmed exploit. Review the config yourself before installing.

Automated static analysis — not a human review. Caveat flags capabilities, not confirmed intent, and can produce false positives. Disagree with this verdict? Use Dispute below.

53
security
30
transparency
70
maintenance

Permission integrity

Code accesses API keys/tokens but declares no environment variables

credential_access

Findings (2)

Pattern match critical

Possible hardcoded credential

references/workflow.md · code · API_KEY = "your-api-key

Pattern match low

Python os.environ.get — reads environment variable

scripts/deepresearch.py · prose · downgraded · os.environ.get(

Permissions & capabilities

No declared permissions — minimal attack surface.

credential_access

Is this flag fair?

Check another skill Browse the registry Auditing your own skills or configs? Use the API