ambiguous@0.9.8
CLI for Ambiguous Workspace — manage docs, tasks, mail, calendar, CRM, and more from the terminal
AI Security Review
scanned 19d ago · by lpm-firewall-aiThis is conditional credential exposure: AMBI_API_URL is unrestricted, and the shared request client forwards existing bearer tokens, including in an activity beacon. The default is the product API and selecting another base requires configuration, so warn rather than block.
Decision evidence
public snapshot- AMBI_API_URL replaces the API base URL without host validation; the default is the product API.
- The CLI can load a token from the environment or saved local, global, and legacy configuration, then build authenticated requests using that base URL.
- Authenticated requests attach the token as a bearer credential and send it to the constructed URL.
- Human account activity triggers a background beacon through the same authenticated request path.
- The user-invoked whoami command also sends the current token to the selected API base.
- The default API base is the package’s product API; the source does not choose an unrelated recipient by default.
- Using an alternate API base requires configuring AMBI_API_URL or the CLI’s API URL setting.
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.8.
See all versions of ambiguous for other recorded verdicts.
- Review the evidence and your use of ambiguous@0.9.8 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.