All plugins

hermes-windows-certificates

Answer "which certificate on this Windows machine expired, and what am I actually trusting": walks the user's and the machine's certificate stores (MY, Root, CA) in-process through crypt32 - no certutil, no PowerShell - and lists every certificate with subject, issuer, validity window, self-signed or not, SHA-1 thumbprint and the store it lives in; the expiry arrives in words ("expired 45 days ago", "expires in 12 days") and the list is sorted with the expired and soon-expiring first. One certificate in full adds the serial number, certificate version, the signature algorithm in words, the public key's algorithm, named curve and size in bits (2048-bit RSA, P-256), and the purposes it is valid for (server authentication, code signing...; no EKU extension is reported as "does not restrict its purposes", which is what its absence means). Find it by thumbprint or by a subject substring, across the user's and the machine's copies. Use it for "why does TLS keep failing on this box", "is the root store healthy", and "which personal certificate ran out". Read-only: stores are opened read-only and only enumerated - nothing is added, removed or changed; no network, no file writes, no elevation, no child processes; 121 certificates across both contexts and all three stores walk in about 8 ms on the writing machine. Windows only. Disclosure - the tools report certificate subjects, issuers, validity windows and thumbprints, to the model; treat the output like the machine's own certificate manager page.

Yicheng-MarkToolsv0.1.0Updated 12 days ago

About

Answer "which certificate on this Windows machine expired, and what am I actually trusting": walks the user's and the machine's certificate stores (MY, Root, CA) in-process through crypt32 - no certutil, no PowerShell - and lists every certificate with subject, issuer, validity window, self-signed or not, SHA-1 thumbprint and the store it lives in; the expiry arrives in words ("expired 45 days ago", "expires in 12 days") and the list is sorted with the expired and soon-expiring first. One certificate in full adds the serial number, certificate version, the signature algorithm in words, the public key's algorithm, named curve and size in bits (2048-bit RSA, P-256), and the purposes it is valid for (server authentication, code signing...; no EKU extension is reported as "does not restrict its purposes", which is what its absence means). Find it by thumbprint or by a subject substring, across the user's and the machine's copies. Use it for "why does TLS keep failing on this box", "is the root store healthy", and "which personal certificate ran out". Read-only: stores are opened read-only and only enumerated - nothing is added, removed or changed; no network, no file writes, no elevation, no child processes; 121 certificates across both contexts and all three stores walk in about 8 ms on the writing machine. Windows only. Disclosure - the tools report certificate subjects, issuers, validity windows and thumbprints, to the model; treat the output like the machine's own certificate manager page.

hermes-windows-certificates

Answer "which certificate on this machine expired, and what am I actually
trusting"
on Windows, from inside Hermes.

win_cert_table({"expired_only": True})
win_cert_table({"query": "DigiCert"})
win_cert_detail({"thumbprint": "cdd4eeae6000ac7f401da5d6cf0b3b3a8887da77"})

The certificate stores are where TLS, code signing and mail encryption live or
die: an expired personal certificate breaks signing, a stale root chain breaks
TLS in ways a browser never shows, and nobody knows what a machine actually
trusts. These two tools read the stores and put the verdict in words.

What the tools report

FieldWhere it comes from
subject, issuer, friendly_nameCertGetNameStringW on each certificate context
valid_from, until, state, notethe validity window, with the expiry in words — 'expired 45 days ago', 'expires in 12 days', 'valid for 300 more days'
self_signedthe subject and issuer DER blobs compared byte for byte (a root signs itself)
thumbprintthe SHA-1 hash property, the key win_cert_detail picks a certificate by
serial, versionthe certificate's own fields; the serial is shown big-endian uppercase
signature_algorithmmapped from its OID: sha256WithRSAEncryption, ecdsaWithSHA384, …
public_keyalgorithm (RSA, EC), the named curve when there is one (P-256…), and the size in bits, read from the modulus or the curve
purposesthe EKU extension's OIDs in words — server authentication, code signing…; no EKU extension is reported as 'does not restrict its purposes', which is what its absence means

win_cert_table walks the current user's and the machine's MY, Root and CA
stores (either scope alone on request), sorts the expired and soon-expiring
first, and filters by name substring, store, or expired_only. A Root store
carries self-signed certificates by design; the notes count them so a hundred
self-signed roots is not read as a hundred problems.

win_cert_detail finds one certificate by thumbprint (punctuation and case
ignored) or by a name substring; several matches come back as a candidate list
with thumbprints to pick from. The user's and the machine's copies of the same
certificate are both reported.

Read-only, and why there is no subprocess

The stores are opened with CERT_STORE_READONLY_FLAG and only enumerated:
nothing is added, removed or changed, and there is no network call, no file
write, no elevation. Everything runs in-process through crypt32 via ctypes
— certutil's output follows the display language and a PowerShell session
costs a quarter of a second before the first row; this walk reads 121
certificates across both contexts and all three stores in about 8 ms. The
enumerator frees each context as it moves; every fact is copied out in Python
before the next step, and the plugin declares no Python dependencies.

Every ctypes prototype is declared with explicit argtypes/restype — on a
64-bit host an undeclared pointer argument is truncated and the call fails
silently. The CERT_INFO layout follows wincrypt.h field for field (Subject
sits after the two FILETIMEs there), so no offset is written by hand. Windows
only.

README from the reviewed commit 11ab27a; it updates when the author re-pins.

More by Yicheng-Mark

18 plugins by Yicheng-Mark in the catalog.

Yicheng-Markhermes-dpapi-secretsResolve Hermes environment variables at startup from a single secret file encrypted with the Windows Data Protection API, instead of keeping provider keys in plaintext in .env or auth.json. Config is secrets.dpapi.map, an ENV_VAR -> store-name mapping (bare names or dpapi:// names) plus an optional file path (default <HERMES_HOME>/secrets.dpapi). The file is one DPAPI blob keyed by the current Windows user profile, so it is unreadable by another Windows account and worthless off the machine; it is written by the bundled CLI (python -m hermes_dpapi_secrets set NAME, value read from a prompt or stdin, never from argv) and only read at runtime. Mapped names that are missing or empty are skipped with a warning; a file that is not ours, a blob this user cannot decrypt, or a payload that is not a flat string map is reported as an error with nothing injected. Disclosure - this source decrypts a file for every Hermes process that enables it: resolved values become environment variables of the Hermes process and its children, exactly like .env entries, so anything that can read that environment can see them. User-scope encryption only (the machine-wide flag is never used and is not exposed), and the at-rest protection is a bar for backups, cloud sync and dotfiles, not a boundary against code already running as the same user. Stdlib-only (ctypes): no Python dependencies, no subprocesses, no network calls, no self-update. Windows only. Applying fetched values stays the orchestrator's job; the plugin never writes os.environ itself. Disclosure — decrypts a DPAPI-encrypted secret file (default <HERMES_HOME>/secrets.dpapi) at startup for every Hermes process that enables it, and the resolved values become environment variables of Hermes and its child processes like .env entries; the encryption is per Windows user and protects backups, cloud sync and copied files, not against other code running as the same user. Local only: no network calls, no subprocesses.CommunitytoolsYicheng-Markhermes-wincredResolve Hermes environment variables from the current user's Windows Credential Manager at startup, instead of keeping provider keys in plaintext in .env or auth.json. Config is secrets.wincred.map, an ENV_VAR -> generic-credential-target mapping (bare names or wincred:// names); each value is read with CredReadW in the current user's vault and handed to the secret-source orchestrator, which applies it with the usual precedence, provenance and conflict rules. Values may be UTF-8 or UTF-16LE (cmdkey and the Credential UI write UTF-16); anything that does not decode to text, or that contains interior NULs, is skipped with a warning instead of being injected as a mangled key. Disclosure - this source reads your Windows Credential Manager: only the generic credentials named in the map, with no enumeration of the vault. Resolved values become environment variables of the Hermes process and its children, exactly like .env entries, so anything that can read that environment can see them. The package is read-only and stdlib-only (ctypes): it never creates, updates or deletes credentials, writes no files, starts no subprocesses, makes no network calls and does not self-update. Windows only. Credential Manager is user-scoped, so this raises the at-rest bar for backups, cloud sync and dotfiles; it is not a boundary against code already running as the same user. Applying fetched values stays the orchestrator's job; the plugin never writes os.environ itself. Disclosure — when enabled, reads only the Windows Credential Manager generic credentials named in secrets.wincred.map (no vault enumeration) and injects them as environment variables of the Hermes process and its children, exactly like .env entries; read-only, stdlib ctypes, no subprocesses, no network, no file writes; user-scoped at-rest protection, not a boundary against code already running as the same user.CommunitytoolsYicheng-Markhermes-windows-appsAnswer "what is installed on this Windows machine": the software inventory behind Apps & Features, swept straight from the four Uninstall registry keys (the machine's 64-bit and 32-bit views plus the user's), so a program is found even when the Settings page hides it - a per-user install that never shows on the machine page came from the user view on the writing machine. Each row carries version, publisher, size in MB, install date and which view it lives in; the same DisplayName in two views is a 32/64-bit dual install, marked instead of listed twice. Entries the publisher asked to hide (runtime packages, update rollups) are filtered out unless asked for. Details one program with every field its publisher wrote and a reading of the uninstall command (MSI product code, setup executable, appx, script) so the next step is known before anything is run; the install folder is checked against disk. Use it for "what did that installer actually register", for inventory before a cleanup, and for "which of the two installs does uninstalling remove". Read-only: registry keys are enumerated and uninstall strings are reported, never run; no network, no file writes, no elevation. The sweep is pure registry - 102 entries in seven milliseconds on the writing machine, the whole table in ten, no PowerShell, no WMI. The plugin declares no Python dependencies. Windows only. Disclosure - the tools report program names, versions, publishers, sizes, install folders and uninstall commands, and what is hidden from Apps & Features, to the model; treat the output like the machine's own Apps & Features page.CommunitytoolsYicheng-Markhermes-windows-devicesAnswer "which device on this Windows machine is unhappy, and what does it need" on Windows: win_device_table lists every present PnP device with its class (System, Net, HIDClass, Display), its status, its manufacturer, its stable device id, and its problem code in words - 28 is one with no driver installed, 10 one that cannot start, 43 one Windows stopped after it reported a failure, 22 one the person switched off on purpose and is not broken - filtering by name or id substring, by class, or to the devices that need attention; devices no longer plugged in are history, left out unless asked for. win_device_detail takes one device by id or name substring and adds the driver behind it from the signed-driver table - name, version, date, provider, signer, INF file, signed or not - or the absence of one, which for code 28 is the same fact said twice; a disabled device gets a note saying it is on purpose, not an alarm. Use it for the Device Manager yellow-mark question without opening Device Manager, for finding what an uninstalled program left behind, and for what changed after an update. Read-only: nothing is enabled, disabled, updated or reinstalled. Both answers come from CIM (Win32_PnPEntity and Win32_PnPSignedDriver, joined by device id), whose property names, enum values and ids do not change with the display language; the human-facing device names localize and are carried through as data, never parsed. The plugin declares no Python dependencies; there is no network call and no file write. Windows only. Disclosure — the tools report device names, manufacturers, device ids and driver versions to the model, and those reveal the machine's hardware inventory and what is plugged into it; treat the output like a Device Manager window opened on their machine.Communitytools

Developer Mode

Explore built-in Hermes toolsets and actions.

HermesAgent

Developer?

Create a Hermes extension for Desktop or agent workflows.

Developer Section