keyhand@0.1.0-pre.4
Keyhand CLI: identities, secrets and login checks for browser agents.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe login trace is transmitted automatically as part of a user-started login, and the packaged README does not clearly disclose that telemetry. The behavior is limited to the package’s own API and login purpose, so this warrants a warning rather than a block.
Decision evidence
public snapshot- The SDK records login structure in a trace that its source labels telemetry.
- The trace can include the identity host and normalized page path; form structure is fingerprinted.
- At the end of a login run, the release body includes the trace and may include browser session state, then posts to the API.
- The CLI defaults to the Keyhand API host, with a user-configurable override.
- The package has no install lifecycle scripts; its declared scripts are build and typecheck.
- The README describes the package as managing browser-agent identities and secrets and running login checks.
- Trace transmission occurs as part of a login run initiated by the user, rather than on installation or import.
- The CLI reads the Keyhand API key through its sign-in flow, and the API URL can be configured.
Source & flagged code
5 flaggedSource gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
dist/keyhand-CHqQyyQf.mjsView on unpkg · L6Package contains a possible secret pattern.
dist/keyhand-CHqQyyQf.mjsView on unpkg · L216Findings
Affected versions and remediation
This report applies to keyhand@0.1.0-pre.4.
See all versions of keyhand for other recorded verdicts.
- Review the evidence and your use of keyhand@0.1.0-pre.4 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.