@flouviahq/cli@1.3.0
CLI de Cord: inicia sesión desde el navegador, configura tu cuenta con IA, integra tu proyecto y prueba webhooks en tu localhost.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe API key is sent to the configured Cord API, which defaults to Cord’s service, and browser login requires user authorization. The npm registry check retrieves version metadata; no malicious install-time or runtime behavior was identified.
Decision evidence
public snapshot- The CLI sends its API key as a bearer token to the configured Cord API base URL, which defaults to https://cordhq.app.
- Browser login sends a device name and generated device ID to the Cord login endpoint, then stores the key returned after authorization.
- The version check fetches the package’s latest version from the npm registry and can be disabled with CORD_NO_UPDATE_CHECK.
- The manifest has a prepublishOnly build script, not an install-time lifecycle script.
- The credential flow is tied to the Cord API base URL and the CLI’s documented login flow.
- The login code presents a browser authorization step before saving the returned key.
- The update check requests version metadata from the npm registry, rather than sending host or project data.
Source & flagged code
3 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/cord.mjsView on unpkg · L89Findings
Affected versions and remediation
This report applies to @flouviahq/cli@1.3.0.
See all versions of @flouviahq/cli for other recorded verdicts.
- Review the evidence and your use of @flouviahq/cli@1.3.0 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.