nokey-vehicle-info
AdvisoryAudited by Static analysis on Apr 30, 2026.
Overview
No suspicious patterns detected.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Pasting these tokens could let the agent query sensitive vehicle information such as exact location, VIN/SN, and lock/window/door status.
The skill requires platform and device access tokens to query vehicle information, including location/status, while the registry metadata declares no primary credential requirement.
本 Skill 使用双 Token 认证机制: - `accessToken`: 平台访问令牌 - `vehicleToken`: 设备访问凭证
Only use this with a trusted provider and least-privilege, revocable tokens; the registry should declare the credential requirement clearly.
Tokens may remain on disk after the conversation and could be read by other local processes or reused later without the user re-entering them.
The skill persists vehicle/API credentials in a plaintext local cache for reuse, without documented permissions, expiration, encryption, or secure credential storage.
缓存文件位置: `~/.nokey_vehicle_info_cache.json` ... 缓存内容: accessToken, vehicleToken, env
Use a secure credential store or environment-scoped secret mechanism, mask stored values, set restrictive permissions, and document how to rotate or delete tokens.
Your vehicle/account tokens could be displayed back to the assistant, terminal history, or logs.
The credential-checking shell snippet prints full secret tokens, which is unnecessary for validation and can expose credentials in logs or chat transcripts.
echo "accessToken: $accessToken"
echo "vehicleToken: $vehicleToken"Do not print full tokens; check only whether values exist and show masked prefixes/suffixes if needed.
A user may provide tokens in the wrong order, causing credentials to be stored or transmitted in the wrong fields and making troubleshooting more likely to expose secrets.
README.md states accessToken first, while SKILL.md states `vehicleToken####accessToken`; this ambiguity affects how high-impact credentials are parsed and sent.
Token 格式：`accessToken####vehicleToken`
Use one consistent token format across all artifacts and validate/mask each field before saving or sending it.
If these values are real or copied from a real environment, they could expose account or vehicle access.
The README includes full token-looking values instead of clear placeholders; even if examples, they resemble real credentials and normalize embedding secrets in documentation.
"accessToken": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9...", "vehicleToken": "5c32cc588a8ef984a02610a59211616c"
Replace realistic credentials with obvious placeholders and scan the repository for accidental secret leakage.
A user looking for the deployment script may fetch or create unreviewed installation code outside the provided artifacts.
The README references a deployment script, but the provided manifest contains only README.md and SKILL.md; this is an incomplete provenance/review-context signal.
运行部署脚本将 Skill 复制到 `~/.agents/skills/`: ```bash ./deploy.sh ```
Do not run any missing or separately obtained deploy script unless its source is trusted and reviewed; include all referenced files in the package.