lithermes-ai
npx/bunx installer for the LitHermes Hermes plugin
This report shows the evidence for lithermes-ai@0.9.9. 1 of 18 known versions is blocked or flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package contains a concealed automatic self-update path from an AI-agent lifecycle hook to a newer release of itself, followed by control-surface mutation. Although it lacks an npm install hook and limits inherited environment variables, the complete hidden self-update chain is concrete and automatic.
Decision evidence
public snapshot- The installed plugin registers a pre-LLM lifecycle hook, so update code runs during agent use.
- The hook fetches the latest version and silently invokes npx for a newer release of this same package.
- The private update command is deliberately omitted from help output.
- The invoked installer replaces the LitHermes plugin payload and writes Hermes configuration without a new user confirmation.
- The package contacts the npm registry as part of this automatic self-update chain.
- package.json has no preinstall, install, or postinstall lifecycle script.
- The update child process removes most inherited environment variables, limiting direct credential exposure.
- The shown update path requests an exact stable version and includes rollback checks.
Source & flagged code
5 flagged · loading sourcePackage source references dynamic require/import behavior.
bin/lithermes.jsView on unpkg · L1Package ships non-JavaScript build or shell helper files.
assets/lithermes-plugin/litgoal/store.pyView on unpkgFindings
Affected versions and remediation
This report applies to lithermes-ai@0.9.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing lithermes-ai@0.9.9. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.