ambiguous@0.9.9
CLI for Ambiguous Workspace — manage docs, tasks, mail, calendar, CRM, and more from the terminal
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe bundle accepts arbitrary environment or saved API URLs and forwards the saved token without a visible destination allowlist, which warrants a warning for conditional credential exposure. The package defaults to its own API and the inspected source does not establish a fixed third-party recipient or covert transfer.
Decision evidence
public snapshot- The published CLI entrypoint loads the distribution bundle.
- The API URL can come from an environment variable or saved local/global config without a visible host allowlist.
- The request layer builds requests to that URL and attaches the saved bearer token.
- Authentication saves the API URL with the credential, so later CLI requests can reuse that destination.
- The default production API is api.ambiguous.ai, and the reviewed sign-in flow exchanges credentials with the selected API URL.
Source & flagged code
3 flaggedBrowser source reuses an authenticated session to collect identity data and mutate account settings while reporting externally.
dist/index.jsView on unpkg · L49Findings
Affected versions and remediation
This report applies to ambiguous@0.9.9.
See all versions of ambiguous for other recorded verdicts.
- Review the evidence and your use of ambiguous@0.9.9 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.