TavernKeeper Scan Report

TavernAI/TavernAI

Commit 08dbd3e Reviewed

No material or immediate-danger concern was identified in this review.

This advisory report describes what the named tools and review process found at one exact commit. Unknown or unobserved behavior may still exist.

0 immediate danger 0 material 12 low

What this review found

No material or immediate-danger item was identified.

Contextual expected matches (11)

OpenGrep reported tavernkeeper.download-and-execute.shell-pipeline

Expected behavior · high confidence

This is a German installation guide showing the standard one-line command the project itself recommends for installing on a Linux server. The user types and runs the command themselves and can see exactly where it comes from. Nothing here is hidden or suspicious; this is the common install style used by many open-source projects.

Technical evidence

Scanner reason: OpenGrep matched static-analysis rule tavernkeeper.download-and-execute.shell-pipeline. The match applies to this repository.

Contextual assessment: The match is inside a documentation page, not executable project code. The flagged text is the project's own documented VPS installer command, which fetches an install script over HTTPS from the project's own website and pipes it into the shell. The source, destination, and action are all fully disclosed to the user, and the command matches the project's stated distribution method referenced in its README. No concealed execution, unexpected destination, or obfuscation is present in the supplied evidence.

Impact: none · Exploitability: unlikely

Developer action: Optionally document a checksum or a download-then-review variant of the install command so cautious users can inspect the script before running it.

Scanner
opengrep 1.26.0
Rule
tavernkeeper.download-and-execute.shell-pipeline
File role
documentation
Source
docs-site/docs/de/docs/installation.md:43-44

OpenGrep reported tavernkeeper.download-and-execute.shell-pipeline

Expected behavior · high confidence

This is the project's English installation guide showing its standard one-line server install command. The user runs it deliberately and can see its source. This is a normal, transparent install pattern used widely in open source.

Technical evidence

Scanner reason: OpenGrep matched static-analysis rule tavernkeeper.download-and-execute.shell-pipeline. The match applies to this repository.

Contextual assessment: The match is in the English documentation page, not executable code. It is the project's own documented installer instruction fetching a script over HTTPS from the project's own domain and piping it into bash. The command is visible to users, matches the distribution method stated in the README, and shows no concealed execution, hidden destination, or unexpected behavior in the supplied evidence.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner
opengrep 1.26.0
Rule
tavernkeeper.download-and-execute.shell-pipeline
File role
documentation
Source
docs-site/docs/docs/installation.md:94-95

OpenGrep reported tavernkeeper.download-and-execute.shell-pipeline

Expected behavior · high confidence

This is the Russian version of the guide showing the project's standard install command with a folder option. The user runs it deliberately and can see where it comes from; nothing is concealed.

Technical evidence

Scanner reason: OpenGrep matched static-analysis rule tavernkeeper.download-and-execute.shell-pipeline. The match applies to this repository.

Contextual assessment: The match is in the Russian documentation page. It is the project's own documented installer command with an install-directory environment variable, fetching the installer over HTTPS from the project's own domain and executing it with a user-supplied target path. The source, action, and destination are disclosed, match the project's README distribution method, and show no hidden or obfuscated behavior in the supplied evidence.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner
opengrep 1.26.0
Rule
tavernkeeper.download-and-execute.shell-pipeline
File role
documentation
Source
docs-site/docs/ru/docs/installation.md:94-95

OpenGrep reported tavernkeeper.download-and-execute.shell-pipeline

Expected behavior · high confidence

This is the Russian guide's standard one-line server install command. It is shown openly to users and comes from the project's own site; this is a common and transparent install style.

Technical evidence

Scanner reason: OpenGrep matched static-analysis rule tavernkeeper.download-and-execute.shell-pipeline. The match applies to this repository.

Contextual assessment: The match is the primary documented installer command in the Russian documentation. It downloads the project's install script over HTTPS from the project's own website and pipes it into the shell, as part of an openly documented VPS installation flow. The behavior is disclosed, proportional to the stated purpose, and involves no unexpected destination or execution path in the supplied evidence.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner
opengrep 1.26.0
Rule
tavernkeeper.download-and-execute.shell-pipeline
File role
documentation
Source
docs-site/docs/ru/docs/installation.md:43-44

OpenGrep reported tavernkeeper.download-and-execute.shell-pipeline

Expected behavior · high confidence

This is the Spanish version of the guide showing the project's standard one-line server install command. The user runs it themselves and can see where it comes from; nothing is concealed.

Technical evidence

Scanner reason: OpenGrep matched static-analysis rule tavernkeeper.download-and-execute.shell-pipeline. The match applies to this repository.

Contextual assessment: The match is in the Spanish documentation page. It is the project's own documented VPS installer command, fetching the installer over HTTPS from the project's own domain and piping it into the shell. The command is disclosed to users, matches the README's stated distribution method, and the supplied evidence shows no hidden destination, obfuscation, or execution beyond the documented install.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner
opengrep 1.26.0
Rule
tavernkeeper.download-and-execute.shell-pipeline
File role
documentation
Source
docs-site/docs/es/docs/installation.md:43-44

OpenGrep reported tavernkeeper.download-and-execute.shell-pipeline

Expected behavior · high confidence

This is the same install command with a folder option, shown openly in the Spanish guide. It does exactly what the documentation says.

Technical evidence

Scanner reason: OpenGrep matched static-analysis rule tavernkeeper.download-and-execute.shell-pipeline. The match applies to this repository.

Contextual assessment: The match is the same documented installer command with an install-directory environment variable in the Spanish documentation. It downloads the project's installer over HTTPS to a user-specified path and runs it, with the source, action, and destination all disclosed to the user and consistent with the project's stated purpose.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner
opengrep 1.26.0
Rule
tavernkeeper.download-and-execute.shell-pipeline
File role
documentation
Source
docs-site/docs/es/docs/installation.md:94-95

OpenGrep reported tavernkeeper.download-and-execute.shell-pipeline

Expected behavior · high confidence

This is the same recommended install command from the guide, just with an extra option to choose the installation folder. It is shown openly to the user, comes from the project's own website, and does exactly what the guide says it does.

Technical evidence

Scanner reason: OpenGrep matched static-analysis rule tavernkeeper.download-and-execute.shell-pipeline. The match applies to this repository.

Contextual assessment: The second match is the same documented installer command with an install-directory environment variable, still inside the documentation file. It downloads the project's own installer over HTTPS and executes it with an explicit, user-supplied target path. The behavior, source, and destination are disclosed, match the project's stated distribution model, and involve no obfuscated or unexpected data flow.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner
opengrep 1.26.0
Rule
tavernkeeper.download-and-execute.shell-pipeline
File role
documentation
Source
docs-site/docs/de/docs/installation.md:94-95

OpenGrep reported tavernkeeper.download-and-execute.shell-pipeline

Expected behavior · high confidence

This is the same recommended install command with a folder-choice option, shown openly in the guide. Nothing hidden or unexpected is present.

Technical evidence

Scanner reason: OpenGrep matched static-analysis rule tavernkeeper.download-and-execute.shell-pipeline. The match applies to this repository.

Contextual assessment: The match is the same documented installer command with an install-directory environment variable, in the documentation file. It downloads the project's installer over HTTPS to a user-chosen directory and executes it, fully disclosed and consistent with the project's stated distribution and update workflow.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner
opengrep 1.26.0
Rule
tavernkeeper.download-and-execute.shell-pipeline
File role
documentation
Source
docs-site/docs/docs/installation.md:43-44

OpenGrep reported tavernkeeper.download-and-execute.shell-pipeline

Expected behavior · high confidence

The flagged text is just a recommended install command in the project's README for setting it up on a Linux server. It downloads an installer from the project's own website and runs it, which is a normal way server software is installed. Nothing here shows the command doing anything sneaky or downloading from an unexpected place, and it only runs when a user deliberately copies and runs it.

Technical evidence

Scanner reason: OpenGrep matched static-analysis rule tavernkeeper.download-and-execute.shell-pipeline. The match applies to this repository.

Contextual assessment: The scanner matched a documentation code block in a README that pipes a remote shell script into a shell interpreter. This is an installation instruction for the project's own server deployment, and the download destination is the project's own website domain, consistent with the repository's stated purpose and its other official download links. The supplied evidence contains no executable project code, no script content, no obfuscated second-stage fetch, and no destination that deviates from the project's own distribution channel. Piping a remote installer directly into a shell is a widely used, user-initiated deployment pattern for server software; the matched text documents an install method rather than concealing execution. The contents of the referenced installer were not supplied, so no behavior of that script is demonstrated by this evidence, but nothing in the supplied data indicates a disguised destination or hidden execution.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner
opengrep 1.26.0
Rule
tavernkeeper.download-and-execute.shell-pipeline
File role
documentation
Source
README.md:39-40

OpenGrep reported tavernkeeper.download-and-execute.shell-pipeline

Expected behavior · high confidence

This is the French version of the guide showing the project's standard one-line server install command. The user chooses to run it and can see its source; this is a normal transparent install pattern.

Technical evidence

Scanner reason: OpenGrep matched static-analysis rule tavernkeeper.download-and-execute.shell-pipeline. The match applies to this repository.

Contextual assessment: The match is in the French documentation page. It is the project's own documented installer instruction, downloading the install script over HTTPS from the project's own domain and piping it into bash. The command is fully visible to the user, matches the project's stated distribution model in its README, and the supplied evidence contains no concealed execution, hidden destination, or obfuscation.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner
opengrep 1.26.0
Rule
tavernkeeper.download-and-execute.shell-pipeline
File role
documentation
Source
docs-site/docs/fr/docs/installation.md:43-44

OpenGrep reported tavernkeeper.download-and-execute.shell-pipeline

Expected behavior · high confidence

This is the same install command with a folder option, shown openly in the French guide. It behaves exactly as documented.

Technical evidence

Scanner reason: OpenGrep matched static-analysis rule tavernkeeper.download-and-execute.shell-pipeline. The match applies to this repository.

Contextual assessment: The match is the same documented installer command with an install-directory environment variable in the French documentation. It fetches the project's installer over HTTPS to a user-chosen directory and executes it, with the behavior and destination disclosed and proportional to the project's stated installation purpose.

Impact: none · Exploitability: unlikely

Developer action: none

Scanner
opengrep 1.26.0
Rule
tavernkeeper.download-and-execute.shell-pipeline
File role
documentation
Source
docs-site/docs/fr/docs/installation.md:94-95

Related contextual observations

Pipe-to-shell installer pattern in documentation warrants no finding on its own

low risk · high confidence

Running an installer straight from the internet is a common convenience, but it means users trust the project's website every time. Letting users download and read the installer first, or checking it against a published checksum, would be a nice extra, though nothing currently shown suggests any problem.

Technical assessment

The pattern of fetching a remote script and immediately executing it is a legitimate, disclosed, user-initiated installation method when the destination is the project's own distribution domain, as it is here. The evidence does not include the installer's contents, so any assessment of the installer itself is outside what this review can demonstrate. Best practice would be to also publish the installer in the version-controlled repository, provide checksums, or offer a two-step download-and-inspect instruction so users can review the script before running it, but the absence of those refinements is a documentation quality consideration, not demonstrated exposure.

Impact: none · Exploitability: unlikely

Developer action: Optionally publish the install script in the repository and link a checksum so users can verify it before executing; no security change is required by the supplied evidence.

Sources:

Coverage and limitations

JavaScript coverage

Tools

Limitations

Technical scan identity