Навыки seo-new-keywords-research История аудитов
📦

История аудитов

seo-new-keywords-research - 3 аудиты

Сравнение версий

Изменения возможностей и находок между проверенными версиями, сначала новые.

ВерсияДатаРезультатПункты проверкиИзменение к предыдущей
v3 Последняя28 окт. 2026 г., 12:35 Подтверждённых находок нет0Возможности не изменились
v2 27 окт. 2026 г., 09:14 Подтверждённых находок нет7Возможности не изменились
v1 20 окт. 2026 г., 14:49 2 подтверждено0Базовая
Версия аудита 3 Последняя

28 окт. 2026 г., 12:35

All 34 static findings are false positives involving Markdown syntax, legitimate CLI operations, provider links, and documented authentication. The skill requires paid lookup approval and explicitly treats retrieved instructions as untrusted data. No evidence of malicious behavior was found in SKILL.md; external package implementation and runtime behavior were not inspected.

1
Просканировано файлов
73
Проанализировано строк
4
Пункты проверки
0
Ложные срабатывания проигнорированы
Аудитор:: codex

27 окт. 2026 г., 09:14

Most detections are Markdown formatting, documentation links, or keyword terminology rather than malicious commands. The workflow executes an external package with paid API credentials, but its implementation was not included in the review.

1
Просканировано файлов
69
Проанализировано строк
11
Пункты проверки
0
Ложные срабатывания проигнорированы
Пункты проверки возможностей (7)

Это реальные локальные возможности, которые могут ожидаться для этого навыка, поэтому они требуют проверки, но не считаются подтверждённым вредоносным поведением.

Высокий
Hidden file in home directory
3. An AIsa key must be available, as `AISA_API_KEY` or from the AIsa CLI (`aisa login` stores it in
The instructions allow the external CLI to use a credential stored in ~/.aisa; the reviewed file does not establish how the package handles it.
Высокий
Generic API/secret keys
3. An AIsa key must be available, as `AISA_API_KEY` or from the AIsa CLI (`aisa login` stores it in
The third-party CLI is configured with an API credential; its handling and network destinations cannot be verified from this file.
Высокий
Generic API/secret keys
4. `GOANYAPI_API_KEY` is optional (a key comes from https://goanyapi.com/r/ga-95708898fb). With it t
The third-party CLI is configured with an API credential; its handling and network destinations cannot be verified from this file.
Средний
Ruby/shell backtick execution
1. Run the pinned release, never a clone of the repository: `uvx new-term-radar==0.6.0 <command> ...
The instructions execute a pinned third-party PyPI package; its implementation was not included in the reviewed files.
Средний
Ruby/shell backtick execution
```bash
The instructions execute a pinned third-party PyPI package; its implementation was not included in the reviewed files.
Средний
Ruby/shell backtick execution
```
The instructions execute a pinned third-party PyPI package; its implementation was not included in the reviewed files.
Средний
Hidden file access
3. An AIsa key must be available, as `AISA_API_KEY` or from the AIsa CLI (`aisa login` stores it in
The instructions allow the external CLI to use a credential stored in ~/.aisa; the reviewed file does not establish how the package handles it.
Аудитор:: codex

20 окт. 2026 г., 14:49

All 29 static findings reflect Markdown formatting, documented provider authentication, relevant links, or ordinary keyword analysis rather than the alleged threats. No evidence found of credential exfiltration or prompt injection in SKILL.md; the external CLI implementation was not provided for review. Separate workflow risks include executing an unpinned repository and initiating paid lookups after cost disclosure without explicit approval.

1
Просканировано файлов
61
Проанализировано строк
6
Пункты проверки
0
Ложные срабатывания проигнорированы

Подтверждённые проблемы безопасности (2)

Средний
Unpinned External Repository Execution
Setup says to clone the repository 'if missing', then runs 'python -m radar keywords'. No reviewed commit or integrity check is required. This allows changing upstream code to execute with local credentials and filesystem access.
The instructions directly connect an unpinned clone with module execution. The external implementation is unavailable, so this identifies supply-chain exposure, not proven malicious code.
Средний
Paid Lookups Without Explicit Spending Approval
Every lookup is paid, but the workflow says 'State the estimate, then' run the command. It does not require approval or a budget ceiling. An agent following these instructions could spend existing account credit without a separate spending authorization.
The text explicitly describes paid calls and proceeds after disclosure, without an approval step. Existing user authorization could mitigate this workflow risk.
Аудитор:: codex