Scan Report
0 /100
flyai-weekend-trip
周末去哪儿2天1夜说走就走方案助手
This is a pure-documentation travel planning assistant (weekend getaways) with no executable code, no credential access, and no data exfiltration — all behavior is correctly declared in SKILL.md.
Safe to install
No action needed. Consider adding a note in SKILL.md clarifying that flyai CLI commands are invoked via the tool harness, not direct shell access.
| Resource | Declared | Inferred | Status | Evidence |
|---|---|---|---|---|
| Filesystem | WRITE | WRITE | ✓ Aligned | SKILL.md declares ~/.flyai/user-profile.md read/write for user preference storag… |
4 findings
Medium External URL 外部 URL
https://img.alicdn.com/... reference/search-hotel.md:44 Medium External URL 外部 URL
https://img.alicdn.com/tfscom/... reference/search-poi.md:32 Medium External URL 外部 URL
https://nodejs.org/ reference/workflow.md:19 Medium External URL 外部 URL
https://registry.npmmirror.com reference/workflow.md:21 File Tree
11 files · 26.6 KB · 863 lines Markdown 11f · 863L
├─
▾
reference
│ ├─
ai-search.md
Markdown
│ ├─
keyword-search.md
Markdown
│ ├─
search-flight.md
Markdown
│ ├─
search-hotel.md
Markdown
│ ├─
search-marriott-hotel.md
Markdown
│ ├─
search-marriott-package.md
Markdown
│ ├─
search-poi.md
Markdown
│ ├─
search-train.md
Markdown
│ ├─
user-profile-storage.md
Markdown
│ └─
workflow.md
Markdown
└─
SKILL.md
Markdown
Security Positives
✓ All 11 files are Markdown documentation — no executable code present
✓ All declared capabilities (keyword-search, search-flight, search-train, search-hotel, search-poi) are documented in SKILL.md with clear parameter descriptions
✓ User profile storage to ~/.flyai/user-profile.md is declared and documented with proper data schema
✓ Qoder Memory mode (search_memory/update_memory) vs file-mode fallback is clearly specified in user-profile-storage.md
✓ No credential harvesting, no environment variable iteration, no sensitive path access (SSH, AWS, .env)
✓ No obfuscation techniques (base64, eval, atob) observed
✓ No remote script execution (curl|bash, wget|sh) present
✓ No supply chain risk — no dependencies (requirements.txt, package.json, etc.)
✓ No data exfiltration, C2 communication, or outbound data transfer
✓ No persistence mechanisms (cron, startup hooks, backdoors)