T08 · Insecure Dependencies
- Location
SKILL.md:16- Finding
Unpinned npm Package Retrieval and Execution
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a clearly disclosed Voyagier travel-booking CLI guide, with expected credential use and real-booking safeguards, but users should treat the external npm install and token configuration carefully.
Before installing, use a pinned and trusted @voyagier/cli version, protect the Voyagier PAT like a password, avoid custom API endpoints unless you control them, and require explicit user approval before any book or send command because those can create charges or email clients.
SKILL.md:16Unpinned npm Package Retrieval and Execution
SKILL.md:24Authentication Token May Be Sent to a Configurable API Endpoint
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
voyagier doctor --json # verify auth + schema + state + version
Get a PAT: voyagier.com → Settings → Personal Access Tokens → Create.
Or use env vars for CI/scripts:
```bash
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- Never output PAT tokens in command output.
- Confirm with the user before `book` and `send` (real charges / real client email).
- Credentials stored at `~/.voyagier/credentials.json` (mode 0600).
- `--dry-run` on `book` previews without creating a checkout.
The skill recommends zero-install execution via npx @voyagier/cli without pinning an exact version. That causes agents or users to fetch and execute whatever package version is current at runtime, increasing supply-chain risk if a malicious or compromised release is published.
No suspicious patterns detected.