@shuv1337/shuvgrok@1.0.7
ShuvGrok: bring Grok into your terminal
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe source establishes automatic shared AI CLI state mutation and execution of an unavailable platform binary, but does not establish concrete malicious behavior such as exfiltration or destructive action. A warning is warranted for the unresolved lifecycle payload and control-surface change.
Decision evidence
public snapshot- An automatic postinstall hook runs package code during npm installation.
- The hook modifies the shared Grok home configuration without an explicit setup command.
- The command trampoline materializes a platform binary and executes it; the binary payload is outside this snapshot.
- No network request, credential collection, or exfiltration logic appears in the inspected JavaScript.
- The installer uses a distinct shuvgrok command and writes an installer marker rather than upstream command settings.
- No self-dependency or nested lifecycle chain is declared.
Source & flagged code
9 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @shuv1337/shuvgrok@1.0.7.
See all versions of @shuv1337/shuvgrok for other recorded verdicts.
- Review the evidence and your use of @shuv1337/shuvgrok@1.0.7 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.