other
- Location
scripts/finance_analysis.py:121- Finding
Hardcoded Financial Results Are Presented as Stock-Specific Analysis
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This finance skill does not show malware behavior, but its valuation and risk commands can present fixed demo numbers as stock-specific investment analysis.
Review before installing. Treat the valuation and risk outputs as illustrative only unless the publisher replaces the fixed values with sourced, stock-specific calculations and adds clear non-advice disclaimers. Pin Python dependencies and understand that enabling TUSHARE_TOKEN may send queried stock symbols to Tushare.
scripts/finance_analysis.py:121Hardcoded Financial Results Are Presented as Stock-Specific Analysis
scripts/finance_analysis.py:56Unsanitized Stock Codes Permit Terminal Escape-Sequence Injection
SKILL.md:116Python Installation Instructions Use Unpinned Third-Party Dependencies
Without declared permissions the skill's intent is opaque and cannot be validated.
The natural-language content of the skill, including its description and usage instructions, is presented only in Chinese. This can violate a language/locale policy when the skill effectively forces a specific language without offering the user an explicit choice or documenting that the skill is region-specific.
This code file contains natural-language strings that establish a fixed language/locale for the skill experience. Under the policy, forcing a specific language without offering the user a choice is a natural-language policy violation unless clearly justified as region-specific.
The DCF valuation function presents itself as a stock-specific valuation tool but emits hard-coded example assumptions and results regardless of the provided stock code. In a finance-analysis skill, this is dangerous because users may rely on fabricated outputs for investment decisions, creating integrity and trust risks even without code execution or data exfiltration.
The relative valuation command claims to assess the specified stock but only prints a static multiples table and a fixed recommendation. In the context of a finance CLI, this can mislead users into believing the result is data-driven, which is a harmful integrity flaw because the recommendation is detached from the actual asset analyzed.
The risk assessment feature outputs fixed metrics, score, and 'low risk' language without evaluating the input stock. In a financial decision-support skill, this is particularly dangerous because it can create false assurance about risk and directly influence user behavior based on fabricated analysis.
The function emits explicit investment recommendations such as '可以买入', '值得买入', and '强烈买入' without any disclaimer that the output is simplified, informational only, and not financial advice. In a finance-analysis skill, users may reasonably rely on these statements for real financial decisions, increasing the risk of harmful overtrust even though there is no code-execution or data-exfiltration component.
SQP-3 applies to natural-language policy issues in all file types. Nearly all user-facing instructions and descriptions are in Chinese, and the document does not indicate that the skill is region-specific or provide any opt-in or alternative language, which can amount to a forced language/locale choice.
This is a markdown file, so SQP-2 applies to omissions in user-facing warnings. The README introduces TUSHARE_TOKEN for Tushare API access, which implies network calls to an external service, but it does not warn users that stock queries and related usage data may be sent to that provider.
This manifest uses Chinese-only natural-language fields such as the description, author name, and tags, with no indication that the skill supports other languages or that the user can choose a locale. Under the policy for natural-language violations, forcing a specific language without user opt-in can be a locale-policy issue.
User-facing docstrings, headers, labels, and recommendations throughout the file are written exclusively in Chinese, which imposes a fixed language/locale on users. The policy allows locale constraints when they are justified or optional, but this file does not provide language selection or explain that it is intentionally region-specific.