Ae1
- Category
- analysis-evasion
- Confidence
- 100% confidence
- Finding
Referenced artifact was not completely inspected
- Content
md - `references/measure.md` - Measure 测量工具
Security audit
Security checks for vulnerabilities and agentic risk
This is a documentation-only MapV-Three GIS skill whose sensitive examples are mostly expected for web mapping work, but users should handle API keys, location data, HTML overlays, and editing examples carefully.
Before installing, be comfortable with Chinese-language docs and with GIS examples that may contact external map or data providers. Keep Baidu/Mapbox/Cesium/Tianditu tokens in secure configuration, avoid pasting real bearer tokens into source, sanitize any untrusted text before rendering HTML overlays or popups, and use explicit authorization and confirmations before adapting the map editing/delete APIs for production data.
Referenced artifact was not completely inspected
- `references/measure.md` - Measure 测量工具
The natural-language content throughout the file is presented in Chinese, and there is no indication that users may opt into another language or that the skill is intentionally restricted to a Chinese-speaking audience. Per the policy, forcing a specific language without user opt-in is a natural-language policy violation.
该 markdown 文件适用 SQP-2。此处介绍了高精地图元素编辑功能,包括添加、更新和删除元素,这些操作会修改后端数据或地图内容,但文档只说明了接口与用法,没有提醒用户这些操作可能造成数据变更、需要权限控制或建议在生产环境谨慎使用。
The document title and the entire skill content are presented only in Chinese, which imposes a specific language choice on users. Under the stated policy, locale or language constraints should either be optional for the user or clearly documented as justified for a region-specific tool.
All user-facing instructional content in this skill file is presented only in Chinese, and the document does not indicate that this locale restriction is optional or region-specific. Per SQP-3, forcing a specific language without user opt-in is a natural-language policy concern.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
});
// 加载 API 数据
const data = await mapvthree.JSONDataSource.fromURL('https://api.example.com/points', {
parseCoordinates: (item) => ({
type: 'Point',
coordinates: [item.location.longitude, item.location.latitude]
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
});
// 加载 API 数据
const data = await mapvthree.JSONDataSource.fromURL('https://api.example.com/points', {
parseCoordinates: (item) => ({
type: 'Point',
coordinates: [item.location.longitude, item.location.latitude]
The documentation includes an example that sends an Authorization bearer token to a remote HTTPS endpoint without any warning about outbound network access, credential handling, or trust boundaries. In a developer-facing skill, this can normalize copying example code that transmits secrets to third-party services, increasing the risk of accidental credential exposure or unintended external data transfer.
This example explicitly demonstrates attaching an Authorization header with a bearer token to a remote request, but provides no warning about secret handling or the risk of sending credentials to external endpoints. In documentation for a data-loading API, this materially increases the chance that users will paste real tokens into sample code and transmit them to untrusted or misconfigured services.
Q: 从 URL 加载时如何传递请求头?
const data = await mapvthree.JSONDataSource.fromURL('https://api.example.com/data', {}, {
headers: {
'Authorization': 'Bearer token',
'Accept': 'application/json'
The title and the entire document are written in Chinese, and there is no indication that users may choose another language or that the skill is intentionally limited to a Chinese-speaking audience. This can violate a language/locale policy when a skill imposes a specific language without user opt-in.
The DOMPoint example builds HTML with template literals and assigns untrusted data fields directly into innerHTML. If developers copy this pattern and the name or description fields come from user-controlled or external data, it can lead to DOM-based XSS and arbitrary script execution in the browser.
The documentation example injects data into innerHTML without any warning about HTML or script injection risks. In a Web-GIS skill, DOMPoint is specifically intended for custom interactive HTML overlays, so unsafe example code is especially likely to be reused in production and can expose applications to XSS.
Line L032 explicitly instructs users to call start() to resume playback, but the surrounding lifecycle documentation at L027-L029 defines the operational methods as track(), pause(), and stop(). This is an active contradiction in the file's own API guidance, not merely an omission.
The file’s instructional content is written entirely in Chinese, including the title and all usage guidance, with no indication that users can choose another language or that the skill is intended only for a Chinese-speaking or region-specific environment. This creates a natural-language locale policy concern because it imposes a specific language by default.
The documentation explicitly demonstrates assigning raw HTML strings to popup.title and popup.content without any warning or sanitization guidance. If developers pass untrusted data into these properties and the component renders via innerHTML or equivalent, this creates a straightforward DOM-based XSS path in a Web-GIS application.
The documentation promotes geocoding, POI search, and route-planning against external providers but does not warn that user-entered addresses, keywords, and coordinates may be transmitted to Baidu Maps or Tianditu. In a GIS/web-mapping skill, these inputs can contain sensitive location data, so omission of data-sharing/privacy guidance can cause developers to unknowingly exfiltrate user data to third parties.
This markdown file includes an example that connects to a WebSocket server and transmits/receives live vehicle tracking data, which can affect privacy and expose operational data. The surrounding documentation does not provide any warning or disclosure about handling sensitive location/telemetry data or securing the connection.
This markdown file declares a required credential (BMAP_JSAPI_KEY) in the manifest header, but the user-facing description contains no warning or guidance about supplying, storing, or protecting that secret. For markdown files, omissions around behaviors affecting privacy or system integrity should be flagged when the skill relies on sensitive credentials.
SQP-3 适用于所有文件。该技能文档全文仅以中文呈现,未提供多语言选项、用户语言选择机制,亦未说明这是面向特定中文用户群或地区的限定文档,可能构成未经说明的语言/locale 限制。
该文件多处说明会从远程 URL、Cesium Ion 或自定义 apiHost 加载数据,其中 TrafficMap3DTiles 还会每 60 秒自动轮询接口。文档没有明确提醒这些功能会持续发起网络请求并向外部服务传输地图查询上下文,可能影响隐私、流量或系统行为可预期性。
This markdown file presents the skill documentation entirely in Chinese, including headings and explanatory text, with no indication that users may choose another language or that the skill is region-specific. Under the policy category, forcing a specific language without user opt-in can be a natural-language policy violation.
The entire skill document is written in Chinese, and there is no indication that the user can choose another language or that the locale restriction is intentional for a region-specific use case. Under the policy rule for natural-language violations, this can be considered a language/locale constraint without user opt-in.
The file’s instructional content is entirely in Chinese, with no indication that the skill supports other languages or that Chinese is a justified region-specific requirement. Under the stated policy, forcing a specific language without user opt-in can be a natural-language policy violation.
This markdown file contains only Chinese-language headings, descriptions, and examples, which can constitute a language/locale policy issue when users are not given an opt-in or alternative language. There is no indication that the skill is intentionally region-specific or that users can choose another language.
This markdown file is written entirely in Chinese, including the title and all usage guidance, with no indication that users may choose another language or that the documentation is intended only for a Chinese-speaking or region-specific audience. Under the stated policy, forcing a specific language without user opt-in can be a natural-language policy violation.
No suspicious patterns detected.