paypal/agent-toolkit

AI review

The extension is a legitimate PayPal API toolkit with no hidden instructions or prompt injection. The only concerns are standard credential handling via environment variables and a CI workflow that writes an NPM token to .npmrc, which is a common practice but could be a risk if the CI environment is compromised.

• medium CI workflow writes NPM token to .npmrc — In .github/workflows/publish.yml:116, the command 'echo "//registry.npmjs.org/:_authToken=$NPM_TOKEN" > ~/.npmrc' writes the NPM token to a file. This is a standard practice for publishing packages, but if the CI runner is compromised or logs are exposed, the token could be leaked. Consider using npm's built-in token authentication via environment variables instead.
• low Environment variable usage for credentials — The toolkit reads PAYPAL_CLIENT_ID and PAYPAL_CLIENT_SECRET from environment variables in multiple example files and the main library. This is expected and secure as long as users do not hardcode secrets. No exfiltration or misuse is present.

Model: deepseek-chat

Static findings