Scan Report
8 /100
gpt-chat
GPT聊天 - 使用GPT模型进行对话和内容生成
Legitimate GPT chat skill with declared network/environment access and no malicious behavior; minor doc-to-config mismatch on the default API proxy.
Safe to install
Consider documenting the default api.openai-proxy.org proxy and pinning node version in package.json for reproducibility.
Findings 2 items
| Severity | Finding | Location |
|---|---|---|
| Low | Undeclared default API proxy endpoint Doc Mismatch | scripts/gpt.js:11 |
| Low | Non-existent GPT-5 model references Doc Mismatch | SKILL.md:16 |
| Resource | Declared | Inferred | Status | Evidence |
|---|---|---|---|---|
| Filesystem | NONE | READ+WRITE | ✓ Aligned | SKILL.md:1 — script execution implies node access; gpt.js:state.json write; gene… |
| Network | READ | READ | ✓ Aligned | gpt.js:36-62 — HTTPS POST to api.openai-proxy.org (or env-configured endpoint) |
| Environment | READ | READ | ✓ Aligned | gpt.js:11 reads OPENAI_API_KEY and OPENAI_API_BASE from process.env |
| Shell | NONE | NONE | — | No shell/shutdown/exec calls; server.js uses Node.js process signals which are s… |
| Skill Invoke | NONE | NONE | — | No cross-skill invocation found |
| Clipboard | NONE | NONE | — | Not accessed |
| Browser | NONE | NONE | — | Not accessed |
| Database | NONE | NONE | — | Not accessed |
1 findings
Medium External URL 外部 URL
https://api.openai-proxy.org scripts/gpt.js:11 File Tree
9 files · 14.1 KB · 530 lines JavaScript 6f · 455L
Markdown 1f · 60L
JSON 2f · 15L
├─
▾
scripts
│ ├─
generate-article.js
JavaScript
│ ├─
gpt.js
JavaScript
│ ├─
server.js
JavaScript
│ ├─
state.json
JSON
│ ├─
test-chat.js
JavaScript
│ ├─
test-key.js
JavaScript
│ └─
test.js
JavaScript
├─
package.json
JSON
└─
SKILL.md
Markdown
Security Positives
✓ No shell execution, reverse shells, or command injection patterns detected
✓ No credential harvesting beyond the declared OPENAI_API_KEY
✓ No base64-encoded payloads, eval(), or obfuscation techniques
✓ No sensitive file path access (~/.ssh, ~/.aws, .env) beyond state.json
✓ No data exfiltration or C2 communication patterns
✓ No supply chain risks — package.json has no external dependencies
✓ HTTPS used for all API calls with Bearer token authentication
✓ State persistence is local-only (state.json in scripts directory)