keychain-hermes

To check for plaintext exposure of API credentials and wallet seeds, you need to scan local keychain directories. This process inspects secret stores to verify sensitive tokens and keys are securely vaulted rather than left readable.

Scanning Git history for committed secrets involves analyzing past commits for exposed tokens or keys. This audit checks repository history to ensure sensitive data was never accidentally committed and recommends remediation if found.

Verifying GPG vault status involves checking the protection state of GPG-encrypted secrets within your local environment. This audit inspects the keychain to confirm that GPG-protected credentials are properly configured and actively secured.

Auditing keychain secrets on Hermes OS requires inspecting local keychain directories for plaintext exposure and GPG vault status. The scan identifies vulnerable tokens, seeds, and keys, then recommends vaulting or rotation actions.

After finding plaintext tokens in your secret store, you should immediately vault the exposed credentials and rotate the compromised keys. The audit provides specific recommendations for securing or replacing any sensitive data identified.

Yes, the secret store audit works without external dependencies, relying solely on internal scripts. It independently inspects local directories, verifies GPG status, and scans Git history to detect exposed credentials.