The earlier review correctly identified an automatic self-update on the documented check path, but its claim that the update is undisclosed conflicts with the CLI’s pre-update notice. The current rules classify a disclosed, product-serving self-update as suspicious; the account code goes to the package’s own entitlement service for the account feature, so it does not add a credential-theft finding.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running the documented `npx kryptheon check` command when the project has an older Kryptheon installation.
Impact
The project’s installed Kryptheon code is replaced and executed during `check`.
Mechanism
The CLI prints an update notice, installs the current Kryptheon version with npm, then runs the project-local CLI with the original arguments. The update is disclosed before it runs, so the current self-update rule calls for a warning rather than a block.
Evidence
bin/kryptheon.jsREADME.mdkryptheon-account.jskryptheon-dashboard-page.jsproject package.json and npm lockfileproject node_modules/kryptheon