@withone/cli@1.55.3
⚠ Under reviewCLI for managing One
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe inspected source does not support the scanner's credential-redirection claim: OpenAI keys go to the OpenAI API, and custom API keys are requested for a user-entered endpoint. The default runtime dependency pgserve is unresolved, so the package cannot be cleared from this inspection alone.
Decision evidence
public snapshot- package.json declares pgserve and a prepare script that only runs the build tool.
- The CLI resolves and launches the pgserve wrapper for its embedded database; that dependency's source was unavailable in this snapshot.
- The OpenAI embedding key is sent to api.openai.com only when the configured provider is OpenAI and a key is present.
- The custom API setup asks for a key for the URL the user entered.
- Inspected source does not establish the scanner's claimed fixed unofficial gateway redirect or credential-redirection persistence.
- The prepare hook runs the build tool; the manifest has no preinstall, install, or postinstall hook.
Source & flagged code
10 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @withone/cli@1.55.3.
See all versions of @withone/cli for other recorded verdicts.
- Review the evidence and your use of @withone/cli@1.55.3 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.