The scripts use file writes, API calls, and environment variables for the declared PDF extraction workflow. The audit confirms the curl-to-shell installer guidance, shell-profile API key persistence, and plaintext HTTP validation calls as security issues. Most backtick, key-name, ID, SQLite, and output-write alerts are benign examples or normal user-directed operations; no prompt injection text was found.
Add to your shell profile (~/.bashrc, ~/.zshrc) for persistence:
The guide recommends hidden shell profile files as the persistence location for an API key. The nearby command shows this is intended credential persistence, not a harmless path mention.
The command appends ANTHROPIC_API_KEY to ~/.bashrc, persisting a credential in a hidden startup file. This can expose the key through dotfile sharing, backups, or local reads.
The setup guide directs users to store an API key in ~/.bashrc instead of a dedicated secret store. That persistent credential handling increases accidental disclosure risk.
Add to your shell profile (~/.bashrc, ~/.zshrc) for persistence:
The line directs users toward hidden shell profile files for persistent API key storage. The concern is contextual but real because the next command writes the secret there.
This writes an API key export into ~/.bashrc. Persistent secrets in hidden startup files are easier to leak through backups, dotfile repositories, or broad local access.
This request sends WFO validation queries over plaintext HTTP. The workflow is user initiated, but the transport creates confidentiality and integrity risk.
This request sends the GeoNames URL over plaintext HTTP, including username and location parameters. The transport can leak data or permit tampered validation responses.
The GeoNames validator builds a plaintext HTTP URL containing GEONAMES_USERNAME and the location query. This exposes the username and query to network observers.
The Linux installation instruction pipes a remote installer directly into sh. This executes downloaded code without inspection or checksum verification.
04
是正措置
この監査で推奨される修正が記録されています。これらを適用する責任はメンテナーにあります。
FIX-001
重大
Remote installer is piped directly to a shell.
Replace the curl-to-shell instruction with package manager installation, manual download, and checksum verification steps.
FIX-002
高
Setup guide recommends storing an API key in a shell profile.
Remove the echo-to-bashrc guidance. Recommend session-only variables, ignored local env files, or a secret manager.
FIX-003
中
Some validation calls use plaintext HTTP.
Use HTTPS endpoints where available, or document the privacy risk and disable those validators by default.
FIX-004
低
External validation sends extracted values to third-party services.
Document each external API destination and recommend skip-validation for confidential datasets.